Usage of schema and configuration files

Do not modify the provided schema files or create custom versions of the schemas. You can also use the provided schema files in custom processes. You can also modify the AuditConfig.xml to change the configuration for audits.
  • Supported to customize directly indicates that you can modify the asset without breaking building block functions. It is recommended that backup the file before you edit it.

  • Supported to create a custom version indicates that you make a copy of the provided schema or configuration (with a different name) and customize it. You can configure properties in processes to utilize your copy.

  • Supported for use in custom processes indicates that there are circumstances where the asset can be used when you create a custom process. In general, if you modifying building block processes that use asset, create a copy of the process.

Schema or configuration file

Supported to customize directly

Supported to create a custom version

Supported for use in custom processes

AddApproverEventData.xsd

No

No

Yes

AddReviewerEventData.xsd

No

No

Yes

ApproverAssignTaskEventData.xsd

No

No

Yes

ApproverDecisionEventData.xsd

No

No

Yes

AuditSchema.xsd

No

No

Yes

RemoveApproverEventData.xsd

No

No

Yes

RemoveApproverEventData.xsd

No

No

Yes

RemoveReviewerEventData.xsd

No

No

Yes

ReviewCompleteEventData.xsd

No

No

Yes

ReviewerDecisionEventData.xsd

No

No

Yes

RSS20.xsd

No

No

Yes

SearchResult.xsd

No

No

Yes

StageCompleteEventData.xsd

No

No

Yes

StageStartEventData.xsd

No

No

Yes

SupportingDocFormData.xsd

No

No

Yes

UpdateStageDurationEventData.xsd

No

No

Yes

AuditConfig.xml

Yes

No

Yes

// Ethnio survey code removed