You do not have permission to edit this page, for the following reason:
You can view and copy the source of this page:
Return to Configuration.
The Configuration tile is used by an Administrator to setup various entities of ICM.
The structure of an Agreement in ICM is based on the concept of Contract Types. These are user-defined workflows (as opposed to rule-based) and are of following types:
Attributes or metadata are the key components of an Agreement. Attribute data is displayed on contracts and associated documents.
Attributes are of two types:
Users with Administrator privileges can only create rules to create Requests or Agreements in ICM using the Rules tile. For example, you can create a Rule for an Agreement to get the Supporting Documents auto attached at the predefined state.
Using Rules you can ensure that:
In ICM, you can create and use the Masterdata for your Agreements.
ICM provides an Alias for Masterdata using the AliasMaster entity so that all Masterdata values that are related can be linked and searched in one-go. You can create an alias on Global Attributes and Template variables (marked as global), not the Contract Type attributes.
ICM has now introduced the capability to copy the role-based team members while creating associations so that the user have the privileges for associated documents as they do for the parent entities. This is achieved by configuring Contract Types.
Related Topics: Contract Type | Attribute | Rule | Masterdata | Alias Master | Cascade Team
You do not have permission to edit this page, for the following reason:
You are not allowed to execute the action you have requested.
You can view and copy the source of this page:
Return to Configuration.