Using policy and behaviors

The Dynamics GP Service framework uses policies to enable a service administrator to specify important characteristics of a service operation. In the Dynamics GP Service framework, each create, update, delete, or void method requires a policy. You need to add a policy for each method you create that is one of these types.

When you create a policy, decide whether to add behaviors to the policy. Behaviors allow your service administrator to configure a characteristic for that method. For example, you could add a behavior that causes a create policy to use a specified value as the default value of a document data member. For more information about how to add policy metadata to the Dynamics GP Service, see Adding Policy Metadata.

To add new policies and behaviors, add policy metadata to the Dynamics GP Service. Use the metadata to define the policy and the configurable behaviors for your methods. To configure your policy behaviors, use the Dynamics Security Console.

To implement a policy in the business logic for the service operation, you use the XSLT template for that operation. As a result, you need to identify the data members in your documents that are impacted by policy. For example, assume you defined a behavior to specify a default value for a data member when a document is created. In the XSLT template that transforms the service document being created into the eConnect XML that will be written to the Dynamics GP database, the XSLT code will examine the policy information and then set the appropriate data member to the default value.