Since you cannot edit the QAD-supplied profiles or create a new one, you must copy an existing profile and modify it. To create a copy and modify a profile, follow these steps.
Select the source profile from the navigation tree. If it is a QAD-supplied object, the only button active is Copy.
Open the nodes in the profile in the navigation tree to view the data objects in the profile.
Click Copy. The new profile is created including all related data objects. The new profile definition screen displays. A new name is provided for the profile by default.
Note: Profile QDoc names cannot contain spaces. If a business object name contains spaces, the system automatically removes them in the corresponding default profile name.
Enter values for the new profile as follows:
Update the name as required. Profile QDoc names cannot contain spaces. If you try to save a profile with spaces in its QDoc name, an error message is displayed.
The business object this profile is based on displays in this field.
For eB2.1 or above databases, specify the domain associated with the profile. If you leave this field blank in eB2.1 or above, the profile applies to all domains in the database. If a domain value is specified, the profile only sends QDocs for events extracted from the specified domain.
For other application types, you can use domain according to your own business requirements or leave it blank.
Specify the entity you want to create the QDoc for.
If you leave the field blank, the profile will create the QDoc for all entities.
No edit allowed. This displays the date and time this profile was last saved.
Choose a profile type. The profile type identifies the response type so that the response can be parsed correctly.
Data Synchronization: The subscriber of the profile is another instance of QAD Enterprise Applications or an add-on application. You normally use this profile type for data synchronization.
QAD Alerts: The subscriber of the profile is QAD Alerts. For information on QAD Alerts, see User Guide: QAD Alerts.
QAD BPM: The subscriber of the profile is QAD BPM. For information on QAD BPM, see User Guide: QAD BPM.
Enter a description of the object. Consider including the creation date, object author, and purpose.
Indicates a QAD-standard profile.
Indicates whether this profile will send delta QDocs or complete QDocs. A delta QDoc excludes non-primary elements of the business object that have not changed since the last update. If a field is tagged Always Publish in the business object, it overrides the delta setting here.
Use this to distinguish between QAD Enterprise Applications QDoc versions. This is the version designation that appears in the QDoc headers and is one of the values required to validate the QDoc.
If using the QDoc XML Syntax setting of Other, specify a URL for QDocs generated using this profile. You do not have to specify a namespace if using an XML Syntax setting of 1.1 or 1.0. Like the QDoc version, the QDoc namespace is a required value in the QDoc headers to validate the source of the QDoc.
Specify the name of the root node in the QDoc XML.
If you select this field without specifying an operation program, an operation node will be included in every data object in the QDoc, and the message will be compared to the last successful message sent to the subscriber to determine the operation of each data object. If you select the field and specify an operation program, the program must determine what the operation is and enter the result into a field on each data object in the profile.
If you leave the field blank, the QDoc will not contain an Operation node and will create a subscriber message based entirely on the current raw message.
If you use the Add Only option to avoid overwriting fields that are locally owned by the target application, you must enable the Detect Operations option.
The archive service will not archive subscriber messages that are required to correctly determine the operation of future subscriber messages.
Publish Unchanged Rows
Select the field if you want to publish unchanged rows in the current message as well as changed rows. To publish changed rows only, clear the check box.
Publish Unchanged Rows only works with Detect Operations and operates in a similar way to delta QDocs, except at the table—rather than the field—level.
Example: You have a sales order consisting of 20 line items, and the price of one line item changes. Select Publish Unchanged Rows to publish the changed row and unchanged rows. To publish only the changed row, clear the check box.
Enter the name of the operation program to use with this profile. This option is used in conjunction with the Detect Operation check box. The operation program you enter must be a Progress (.p) program contained in the PROPATH.
Only select this check box if you want to perform an operation calculation, or if you want the operation value to be entered into a different field than the operation node. For details about using operation programs in profiles, see Parameter Data
Click Add Custom Field to add a new field to the data object.
Adding a Custom Profile Field
Enter a field name, specify a data type, and add a fixed value or Progress calculation program if needed. The field name must contain only alphanumeric characters; the name is validated to ensure no illegal characters are included and that the field name is a valid XML node.
To delete a custom field, click in the selection box to the left of the field and click Delete Custom Field.
Select or clear the check boxes for event types as required to determine which events must occur in order for the profile to be published. By default the Listen check box is enabled for all event types for the profile.
The event types that are available are the activated event types for all data objects in the business object related to the profile. Hence these event types are related to the profile as a whole, not to a specific data object. The profile event types do not appear when editing a data object for the profile.
Click Save to save the new profile and any changes you have made.