Policy overview

Each create, update, and delete operation has a policy object that is passed with the operation. This policy object specifies the set of behaviors for the operation. Each behavior controls one characteristic for the operation being performed. For instance, the policy for the CreateCustomer method has the behavior named "Create Active Behavior". This behavior controls whether the customer being created is set to the active or inactive state.

Behaviors are classified as internal or external. An internal behavior is one that can be specified by only the Dynamics GP service administrator. An external behavior is one that can be specified by the application that is calling the method and passing in the policy object.

Hint: Some policies do not have any behaviors, but the policy object must still be passed with the call to the Dynamics GP service method.

Policy instances

Each company has a set of default policies that are always available. There is one default policy for each Dynamics GP service operation that requires a policy. Within a company, additional versions of the policy (with different behavior settings) can be created for each role defined in the Dynamics Security Service. Each of these is called a policy instance. When a web service application retrieves a policy to use, the Dynamics GP service applies logic to ensure the appropriate policy instance is returned. You will learn more about this in Using policy in a web service application.

Policy reference

The Dynamics GP Web Service Reference help file contains a complete list of the default policies that are defined for the operations in the Dynamics GP service. All of the behaviors (including internal and external) are listed, including a description of what the behavior does.