ICIHelp8.2 - User contributions [en]

Implementing the rule approval workflow

2021-12-20T06:39:33Z

AR:

= Implementing the Rule Approval Workflow =

Approval Rule workflow helps in deciding the sequence in which the Rule will be sent for approval to more than one approver. 

Here is how the rule approval flow is implemented:

#The step number (for example, step 4 ) indicates the sequence at which the document should be sent to the approver for approval.
#At a particular step number, the system will wait for all the approvers included (if all 3 should approve), so that primary owner can add feedback of all the three approvers, even if one rejects.
#Approval process flows in parallel for the Approvers and Deviation Approvers that have the same step number.
#If an Approver appears in two different rules at the same step number, both the rules can be approved at the same time.
#If you need approval from 3 out 5 approvers, and first 3 approvers reject the Agreement, system will directly take the Agreement into Draft state.
#At the end of every approval, system evaluates the rule and then the system updates the approver team according to the changes done by primary owner.
#After the approval and deviation approval is complete, the agreement goes to the External Signatory, Internal Signatory, and then to the Reviewer. (The process flow for external and internal signatory may differ for different organizations.)
#If a rule needs an approval from 'n' number of approvals, and a user reduces the number to less than 'n', then ICI will take the approval from all the remaining approvers in a particular step.

Admin Task

2021-12-18T12:55:59Z

AR:

= Admin Task =

== Search Sync ==

The Search Sync tool gets data from Icertis Search for a given instance’s ''Sys Id'' and synchronizes it if required. Using the fetched ES value, the tool validates if the Sys Id is the latest for the respective instance or if a sync is required. The Administrator can access this option from the "Admin Task" on the "Admin" tile.

If the key exists, the latest value from ES will be displayed. If the key does not exist, the system displays an error message indicating that the value could not be fetched for the provided Sys Id. The Sys Id can be provided as input CSV file or as comma separated. Either comma separated Sys Ids can be entered or a CSV file can be uploaded.

This helps to make the entity search more streamlined and efficient. Users can quickly refer to related agreements at the time of deals or audits.
<div class="note-box">'''Note''': Data can be fetched from only one instance at a time. A dedicated key must exist for ES sync to work with "Sys ID".</div>
You can search the documents that an Agreement is linked to.

To use the Search Sync Tool:

1. '''Click''' Admin tile on the Home page and then '''click''' "Admin Task".
<div class="image-green-border">[[File:Admin Task Option1.png|720px|Search Sync 1]]</div> <div class="image-green-border"> </div> <div class="image-green-border">The Admin Task page opens</div>
2. '''Click''' "Search Sync"'' ''menu from the left pane.
<div class="image-green-border">[[File:Search Sync Menu2.png|720px|Search Sync Menu2.png]]</div> <div class="image-green-border"><div class="image-green-border">
3. '''Select''' the “Entity Type” from the drop-down to sync data to the Icertis Search. For example, Agreement.

4. '''Select''' the “Contract Type” from the drop-down''.''

To get the “Sys Ids”'','' you can either use the “Upload CSV” feature to upload the .CSV Agreement or enter the Sys Id using comma separated values in the box.

[[File:Entity Type1.png|720px|Entity Type.png]]
</div> </div>
5. '''Click''' the “Upload CSV” button to upload the CSV document. The “Upload Document” window opens.

6. '''Click''' the “Select File” button to upload a CSV file and add a note, if required.
<div class="image-green-border">[[File:UploadSysID File1.png|720px|Upload Sys ID File.png]]</div> <div class="image-green-border"> </div>
7. '''Click''' the "Upload" button. The file is uploaded to the "File Path" displayed''.''

''   '' If the uploaded file format is incorrect, an alert message is displayed. The supported file formats will be also be displayed.
<div class="image-green-border">[[File:Search Sync File Error1.png|720px|Search Sync File Error1.png]]</div>
8. '''Click''' the "Sync" button. The "Sync Request Accepted" message is displayed. 
<div class="image-green-border">[[File:Search Sync Accepted.png|720px|Search Sync Accepted.png]]</div>
9. Users can now get data from ES for a given instance’s SysId and can check if it has the latest value or if sync is needed.

10. '''Select''' "Get ES Value".

11. Enter the SysId and '''click''' the "Go". If the key exists, the latest value from ES will be displayed. If the key does not exist, the error message "Please enter valid SysId" is displayed.
<div class="image-green-border">[[File:8.0-Search-Sync-GET-ES.PNG|720px|8.0-Search-Sync-GET-ES.PNG]]</div>
 
<div class="note-box">'''Note''': Data can be fetched from only one instance at a time.</div>
== Legacy Upload ==

Organizations may have a large number of existing Agreements that are created outside of ICI platform. These are henceforth referred to as Legacy Agreements. Organizations may want to import these Agreements to ICI to leverage its vast capabilities and manage all Agreements within a single platform.<br/> The Legacy Upload feature enables ICI Administrator to easily upload in bulk the legacy agreements that were created outside of ICI. This feature enhances productivity by allowing you to upload a large volume of existing Agreements and other entities using Excel.

The highlights of this feature are : 

*Uploading Agreements, Teams, Notes and Commitments in bulk.
*Uploading Associations, Masterdata, User Information and Amendments in bulk.
*Scheduled batch processing for improved performance.
*Enhanced validations, including the ability to exclude the specified attributes from being validated. 
*Ability to view logs and reporting of success and failure statuses for validations and uploads.

You can use the utility to upload the following entities: 

*Agreements 
*Amendments
*Associated Documents (with or without workflow)
*Masterdata (with or without workflow)
*Team, Notes, and Commitment
*User details

Refer to the  [[Legacy_Upload|Legacy Upload]] page or link for more details.

== Translations Editor ==
<div class="image-green-border">
The ICI platform is available in different languages and different languages label text are available for localization. However, to make any changes to the localization values, users had to reach out to the Solutions Engineering or Database teams. Sometimes, these changes were minor and of low complexity, but the turnaround time was substantial.

Hence, a self-service "Translations Editor" tool has been introduced that contains all strings that are localized.

Users can now download all keys and their localization values as an Excel file, modify multiple values, and upload the modified changes to ICI. Once the values are updated in ICI, the caches are updated automatically to avoid the cache flush and server restart. This has significantly enhanced productivity as the turnaround time to update the Resource Key values has been eradicated.

Using this tool, users can now:

*Search for a specific string using the search bar and update the Resource Key value for Language and Locale.
*Update multiple language strings by selecting and saving the Resource Key value.
*Download and upload the localization key values using Microsoft Excel.
*View the modified values in the ICI instance immediately.
</div>
To use the Translations Editor Tool:

1. C'''lick''' Admin tile on the Home page and then '''click''' "Admin Task". The "Admin Task" page opens.

2. '''Select''' the "Translation Editor"task from the left pane''.''

Users can update translations in the following ways:

*For selective editing, select a language and a resource key to update the translations.
*For bulk editing and updation of multiple languages and resource keys, use the Download / Upload option to download an MS Excel sheet.

===== Selective Editing to Update Translations =====

For editing Resource Key values selectively:

1. From the "Select Language" drop-down, select a language in which you want to edit the labels. For example, français (French).
<div class="image-green-border">[[File:Select Language1.png|720px|Select Language.png]]</div>
The Resource Key and respective values of the selected language are displayed.
<div class="image-green-border">[[File:Resource Key List1.png|720px|Resource Key List.png]]</div>
2. '''Ente'''r a "ResourceKey" value in the "Search" field to edit. For example, default. All ResourceKey(s) with the "Par défaut (default)" values from the French language are displayed.
<div class="note-box">'''Note:''' ResourceKey is a unique key by which the application gets its label text for different languages.</div>
3. '''Click '''the "Edit this Resource Key for the Multiple Languages"'' ''icon [[File:Edit Resource Key Icon.png|20px|Edit Resource Key Icon.png]] in the "Actions" column on the right.
<div class="image-green-border">
You can change the key for a single language or for multiple languages as required. For example, change "Par défaut to défaut" in French or "Predeterminado" in Español (Spanish) to "Defecto".

[[File:Edit Resource Key1.png|600px|Edit Resource Key.png]]

4. '''Click''' the "Update" button.

5. After the "Resources Updated Successfully" message is displayed.

You can select the respective languages (French or Spanish) to verify that the resources have been successfully updated.
</div>
===== Bulk Editing in Multiple Languages =====

 For editing Resource Key values of multiple languages in bulk:

1. '''Click''' the "Download File" button. A Microsoft Excel file (named BulkActionWorkBookStringResource) that contains all the Resource keys and values for all supported languages in ICI is downloaded.
<div class="image-green-border">[[File:Translations Bulk Upload1.png|720px|Translations Bulk Upload1.png]]</div>
2. '''Open''' the downloaded Microsoft Excel file.

3. '''Click''' "Enable Editing". All ICI supported language Resource keys and their respective values are displayed.

4. '''Edit''' the ResouceKey of multiple languages as required.

5. '''Save''' the Excel file.

6. '''Click''' the "Upload File" button. The "Upload Translations" window opens.

7. '''Click "'''SelectFile". The "Open"''window opens.''

8. '''Select''' the updated Excel file.

9. '''Click''' "Open". A warning window opens indicating that this is a heavy operation and can potentially affect overall application performance.

10. '''Click''' "Ok". The "Upload Summary" displays the number ''of "''Records Uploaded", "Records Processed", and "Records Updated Successfully"''values.''

11. '''Click''' "Close". The label translations have been achieved for multiple languages in bulk.

== Data Management ==

Moving one step ahead in the self-service, ICI now allows performing data management activities for entities in all workflow stages.

The data management activities introduced with this release are update and delete operations for Agreements, Associated Documents, Contract Requests, User Information, Files and Attributes. These self-serve data management operations will empower administrative users to troubleshoot data inconsistency issues on their own.

However, users are advised to execute these operations cautiously as the data fix does not go through necessary business validations and are performed directly in the database itself. Furthermore, updating or deleting data through the data management tool cannot be undone and will not trigger any underlying rules, workflows, notifications, triggers, or integrations. Therefore, it is recommended to follow standard ICI workflows for any major or entity state modifications.
<div class="note-box">'''Note:''' The type of attributes such as Expressions, Conditional, Multi-select Lookup, Script, and System will remain non-editable and cannot be updated through the data management tool.</div>
By default, the Data Management utility is enabled and can be controlled through the technical configuration.

Administrators can perform the following actions from the Data Management page:

*Replace User
*Delete Entity
*Update Entity

A data management notification will be sent to a user who performs any data fix action along with primary owner, secondary owner and contract manager upon the data fix task completion with the details of the entity and modified data.

Please refer [[Notifications_Dashboard|"Notifications Dashboard"]] page for notification details.
<div class="note-box">'''Note:''' Data Management tools do not support updating data for any add-in applications. The validations will not be performed for any data fixed through Data Management tools.</div>
=== Replacing a user with multiple users ===

In ICI, administrators can replace user(s) with all associated records using the “Replace User” functionality. In practice, administrators may need to replace a user with more than one user. For example, if a user leaves the organization, the administrator may want to replace that user by dividing agreements associated with that user, in subsets, among multiple users. This would help the organization to balance the workload within its employees.

Administrators can now: 

*Replace the user with one or more users by selecting the entity and all/selective instances of that entity and create a saved search for an input to replace users.  
*Validate the replaced user role against the assigned role. 
*Get a notification on adding or completing a task.

This capability is available across ICI for contract requests, agreements, associations, masterdata, template and clause teams, user groups, and rules. A separate data management user interface is provided for these admin actions.
<div class="note-box">'''Note:''' Data Management tools do not support updating data for any add-in applications. The validations will not be performed for any data fixed through Data Management tools.</div>
To replace user:

1. '''Navigate''' to the "Data Management" page.

2. '''Select '''"Replace User" in the "Action" field. The fields to enter details such as user to be replaced, user to be assigned, replacement criteria, and entity are displayed.

3. '''Click '''Add User icon corresponding to the "Replace User" field. The "Search User" drawer opens.
<div class="image-green-border">[[File:Replace User1.png|720px|Replace User1.png]]<br/> ''' '''<br/> 4''. '''''Search '''and '''select '''a user you want to replace.</div> <div class="image-green-border">[[File:Select User1.png|720px|Select User.png]]</div> <div class="image-green-border"><br/> 5. '''Click '''"Add". The user will be entered in the "Replace User" field.</div>
6. '''Search '''and '''Add '''the "Assign To" user with whom you want to replace the user.
<div class="image-green-border">[[File:Assign Replace User.png|720px|Assign Replace User.png]]<br/>  <br/> 7. '''Select '''"Replace Based On" criteria from options:</div>
*Saved Search
*Contract Type
*All Instances For Selected Entities 

'''Saved Search'''<br/> Administrators can replace a user in selective instances of an entity with different users by selecting a relevant Saved Search configured for that entity and user.

For example, user John Watson is added to the Teams of agreements from India and US regions. He can be replaced by multiple users by splitting agreements under his name in subsets using Saved Searches, one for agreements for the India region and the other for agreements in the US region. A saved search "JonhWatson_India_Agreements" can be created for John Watson's’s India region agreements and assigned to a user Johne Doel.  A saved search "JonhWatson_US_Agreements" for his US region agreements can be created and assigned to another user, for example, Prajakta.
<div class="note-box">'''Note: '''You can create "Saved Search" for Agreements from the Agreement Index page. Filter the records from "Refine View" in the left and "Save View". Then can update the view if required by selecting it under "More Views" in the title bar.</div>
7.1 '''Select '''"Saved Search". The "Entity" and "Saved Search" fields are displayed.

7.1.1 '''Select '''the Entity for which you want to replace the user in its instances "Team". For example, "Agreement Team".

7.1.2'''Select '''the "Saved Search". For example, "John_Watson_India_Agreements". Users need to create a saved search on the entity for which they want to replace a user in its instances team.

7.1.3 '''Click '''"Submit". The success message flashes displaying a "Replace User action is submitted successfully".
<div class="image-green-border">[[File:Saved Search1.png|720px|Saved Search.png]] </div> <div class="image-green-border">''' '''</div>
'''Contract Type'''<br/> This option replaces a user added in "Rules" actions configured on the selected "Contract Type" by the "Assign To" user.

7.2 '''Select '''"Contract Type". The "Entity" and "Contract Type" fields are displayed.

  7.2.1 '''Select '''the "Entity" as "Rules".

  7.2.2 '''Select '''"Contract Types". For example, "Standard Document Master".

  7.2.3 '''Click '''"Submit". The success message flashes displaying a "Replace User action is submitted successfully".
<div class="image-green-border">[[File:Contract Types Data Management.png|720px|Contract Types Data Management.png]]</div>
'''All Instances For Selected Entities'''

This option replaces a user in the Team of all instances of the selected entity by the "Assign To" user.

7.3 '''Select '''"All Instances For Selected Entities". The Entity field is displayed.

7.3.1 '''Select ''''Entity". For example, "Agreement Team". 

7.3.2 '''Click '''"Submit". The success message flashes displaying a "Replace User action is submitted successfully".
<div class="image-green-border">[[File:All Instances For Selected Entities.png|720px|All Instances For Selected Entities.png]]</div>
The task is submitted and will be scheduled and processed according to the "Time zone" set in "User Preferences". The audit details are captured and displayed in the Agreement History tab.

Users can access the notifications in the "Data Management" category from the "Notifications Dashboard" from the bell icon on the top right. The notification contains a link to view the summary of the Replace User task. 
<div class="image-green-border">[[File:Data Management Notifications Dashboard1.png|600px|Data Management Notifications Dashboard1.png]]</div>
=== Deleting an Entity ===

When you want to remove certain records as a part of data clearance process, Administrators can mark the entity instances as deleted for you using Data Management tools.
<div class="note-box">Note: Deleting data this way, through data management tools, will not trigger any rules, events or integrations configured on concerned entities.</div>
When the entity instance is deleted, its linked child records will also be marked as deleted as per the standard behavior and will not be accessible. Administrators can delete instances of agreement, amendment, contract request and associated document entities in any workflow states.

To delete an entity instance:

1. '''Navigate '''to the "Data Management" option as mentioned in the above section.

2. '''Select '''the "Delete Entity" in the "Action" field. The fields to select an entity and its instance to be deleted, are displayed.
<div class="image-green-border">3. '''Select '''the "Entity" which you want to delete. For example, "Agreement".</div>
4. '''Click '''the Search icon corresponding to the "Entity Instance" field to select an instance of that entity to be deleted. The Lookup Search "Select Agreement" drawer for the selected entity opens.
<div class="image-green-border">[[File:Select Instance Entity1.png|720px|8.0-Data-fix-tools-Deleting.PNG]]</div>
5. '''Choose '''an instance and '''click "'''Select".

6. '''Click "'''Submit". The confirmation window appears'''.'''

7. '''Click '''"Yes". The selected entity instance will no longer be accessible.
<div class="note-box">'''Note: '''When you delete an entity instance, its linked associations will also be marked as deleted as per the standard behavior.</div>
=== Updating an Entity ===

There may be a business requirement to update selective data as a data maintenance and management process without processing any underlying actions associated with the update. Also, there may be a case, where a user does not have required access privileges to modify specific data. In such cases, Administrators can update data for you using Data Management tools.
<div class="note-box">'''Note:''' Updating data through data management tools will not trigger any rules, events, workflows or integrations configured on concerned entities.</div>
Administrators can update instances of agreement, amendment, contract request, associated document, masterdata, user information and commitment entities. Business users can view the data modifications done for a specific record in the audit logs from the History tab on the entity details page.

To update entity:

1. '''Navigate '''to the "Data Management" page as mentioned in the above section. 

2. '''Select '''the "Update Entity" option in the "Action" field. The fields to select an entity, its instance, and attribute are displayed.

3. '''Select "'''Entity". For example, "Masterdata".

4. '''Click '''the Search icon corresponding to the "Entity Instance" field to select an instance of the entity that you want to update. The Lookup Search "Select MasterData" drawer for the selected entity opens.

5. '''Select '''an instance. All supported attributes from the selected entity are displayed in the Attribute dropdown field.

6. '''Select '''the "Attribute" whose value you want to modify. For example, "Name". The attribute’s value from the selected instance is displayed for a user to edit.
<div class="image-green-border">7. '''Edit '''the attribute value as per the requirements. For example, enter a value for Name''.''</div> <div class="image-green-border">''[[File:Select Attribute.png|720px|Select Attribute.png]]''</div>
8. '''Click '''"Submit". The confirmation window opens.

9. '''Click '''"Yes" to proceed. The attribute of the entity instance will be updated with the new value.
<div class="note-box">'''Note:''' The Commitment attributes such as Commitment Code, Recurring Commitment, Commitment Frequency, Commitment type, Business Owner, Start Date and End date cannot be updated using Data Management actions.</div> <div><div><div> </div> <div id="_com_1">'''Related Topics: '''''<b>[[Agreement_Management|Agreement Management]] | [[Managing_Organization|Managing Organization]] | [[Managing_Users|Managing Users]] | [[Managing_User_Groups|Managing User Groups]] | [[Managing_Security_Groups|Managing Security Groups]] | [[Application_Settings|Application Settings]] | [[Notification_Settings|Notification Settings]] | [[Currencies|Currencies]] | [[Reasons|Reasons]] | [[Deleting_an_Agreement|Deleting an Agreement]] |[[Legacy_Upload|Legacy Upload ]]| [[Notifications_Dashboard|Notifications Dashboard]]</b>''</div> </div> </div>

Admin Task

2021-12-18T12:37:09Z

AR:

= Admin Task =

== Search Sync ==

The Search Sync tool gets data from Icertis Search for a given instance’s ''Sys Id'' and synchronizes it if required. Using the fetched ES value, the tool validates if the Sys Id is the latest for the respective instance or if a sync is required. The Administrator can access this option from the "Admin Task" on the "Admin" tile.

If the key exists, the latest value from ES will be displayed. If the key does not exist, the system displays an error message indicating that the value could not be fetched for the provided Sys Id. The Sys Id can be provided as input CSV file or as comma separated. Either comma separated Sys Ids can be entered or a CSV file can be uploaded.

This helps to make the entity search more streamlined and efficient. Users can quickly refer to related agreements at the time of deals or audits.
<div class="note-box">'''Note''': Data can be fetched from only one instance at a time. A dedicated key must exist for ES sync to work with "Sys ID".</div>
You can search the documents that an Agreement is linked to.

To use the Search Sync Tool:

1. '''Click''' Admin tile on the Home page and then '''click''' "Admin Task".
<div class="image-green-border">[[File:Admin Task Option1.png|720px|Search Sync 1]]</div> <div class="image-green-border"> </div> <div class="image-green-border">The Admin Task page opens</div>
2. '''Click''' "Search Sync"'' ''menu from the left pane.
<div class="image-green-border">[[File:Search Sync Menu2.png|720px|Search Sync Menu2.png]]</div> <div class="image-green-border"><div class="image-green-border">
3. '''Select''' the “Entity Type” from the drop-down to sync data to the Icertis Search. For example, Agreement.

4. '''Select''' the “Contract Type” from the drop-down''.''

To get the “Sys Ids”'','' you can either use the “Upload CSV” feature to upload the .CSV Agreement or enter the Sys Id using comma separated values in the box.

[[File:Entity Type1.png|720px|Entity Type.png]]
</div> </div>
5. '''Click''' the “Upload CSV” button to upload the CSV document. The “Upload Document” window opens.

6. '''Click''' the “Select File” button to upload a CSV file and add a note, if required.
<div class="image-green-border">[[File:UploadSysID File1.png|720px|Upload Sys ID File.png]]</div> <div class="image-green-border"> </div>
7. '''Click''' the "Upload" button. The file is uploaded to the "File Path" displayed''.''

''   '' If the uploaded file format is incorrect, an alert message is displayed. The supported file formats will be also be displayed.

[[File:Search Sync File Error1.png|720px|Search Sync File Error1.png]]

8. '''Click''' the "Sync" button. The "Sync Request Accepted" message is displayed. 
<div class="image-green-border">[[File:Search Sync Accepted.png|720px|Search Sync Accepted.png]]</div>
9. Users can now get data from ES for a given instance’s SysId and can check if it has the latest value or if sync is needed.

10. '''Select''' "Get ES Value".

11. Enter the SysId and '''click''' the "Go". If the key exists, the latest value from ES will be displayed. If the key does not exist, the error message "Please enter valid SysId" is displayed.
<div class="image-green-border">[[File:8.0-Search-Sync-GET-ES.PNG|720px|8.0-Search-Sync-GET-ES.PNG]]</div>
 
<div class="note-box">'''Note''': Data can be fetched from only one instance at a time.</div>
== Legacy Upload ==

Organizations may have a large number of existing Agreements that are created outside of ICI platform. These are henceforth referred to as Legacy Agreements. Organizations may want to import these Agreements to ICI to leverage its vast capabilities and manage all Agreements within a single platform.<br/> The Legacy Upload feature enables ICI Administrator to easily upload in bulk the legacy agreements that were created outside of ICI. This feature enhances productivity by allowing you to upload a large volume of existing Agreements and other entities using Excel.

The highlights of this feature are : 

*Uploading Agreements, Teams, Notes and Commitments in bulk.
*Uploading Associations, Masterdata, User Information and Amendments in bulk.
*Scheduled batch processing for improved performance.
*Enhanced validations, including the ability to exclude the specified attributes from being validated. 
*Ability to view logs and reporting of success and failure statuses for validations and uploads.

You can use the utility to upload the following entities: 

*Agreements 
*Amendments
*Associated Documents (with or without workflow)
*Masterdata (with or without workflow)
*Team, Notes, and Commitment
*User details

Refer to the  [[Legacy_Upload|Legacy Upload]] page or link for more details.

== Translations Editor ==
<div class="image-green-border">
The ICI platform is available in different languages and different languages label text are available for localization. However, to make any changes to the localization values, users had to reach out to the Solutions Engineering or Database teams. Sometimes, these changes were minor and of low complexity, but the turnaround time was substantial.

Hence, a self-service "Translations Editor" tool has been introduced that contains all strings that are localized.

Users can now download all keys and their localization values as an Excel file, modify multiple values, and upload the modified changes to ICI. Once the values are updated in ICI, the caches are updated automatically to avoid the cache flush and server restart. This has significantly enhanced productivity as the turnaround time to update the Resource Key values has been eradicated.

Using this tool, users can now:

*Search for a specific string using the search bar and update the Resource Key value for Language and Locale.
*Update multiple language strings by selecting and saving the Resource Key value.
*Download and upload the localization key values using Microsoft Excel.
*View the modified values in the ICI instance immediately.
</div>
To use the Translations Editor Tool:

1. C'''lick''' Admin tile on the Home page and then '''click''' "Admin Task". The "Admin Task" page opens.

2. '''Select''' the "Translation Editor"task from the left pane''.''

Users can update translations in the following ways:

*For selective editing, select a language and a resource key to update the translations.
*For bulk editing and updation of multiple languages and resource keys, use the Download / Upload option to download an MS Excel sheet.

===== Selective Editing to Update Translations =====

For editing Resource Key values selectively:

1. From the "Select Language" drop-down, select a language in which you want to edit the labels. For example, français (French).
<div class="image-green-border">[[File:Select Language1.png|720px|Select Language.png]]</div>
The Resource Key and respective values of the selected language are displayed.
<div class="image-green-border">[[File:Resource Key List1.png|720px|Resource Key List.png]]</div>
2. '''Ente'''r a "ResourceKey" value in the "Search" field to edit. For example, default. All ResourceKey(s) with the "Par défaut (default)" values from the French language are displayed.
<div class="note-box">'''Note:''' ResourceKey is a unique key by which the application gets its label text for different languages.</div>
3. '''Click '''the "Edit this Resource Key for the Multiple Languages"'' ''icon [[File:Edit Resource Key Icon.png|20px|Edit Resource Key Icon.png]] in the "Actions" column on the right.
<div class="image-green-border">
You can change the key for a single language or for multiple languages as required. For example, change "Par défaut to défaut" in French or "Predeterminado" in Español (Spanish) to "Defecto".

[[File:Edit Resource Key1.png|600px|Edit Resource Key.png]]

4. '''Click''' the "Update" button.

5. After the "Resources Updated Successfully" message is displayed.

You can select the respective languages (French or Spanish) to verify that the resources have been successfully updated.
</div>
===== Bulk Editing in Multiple Languages =====

 For editing Resource Key values of multiple languages in bulk:

1. '''Click''' the "Download File" button. A Microsoft Excel file (named BulkActionWorkBookStringResource) that contains all the Resource keys and values for all supported languages in ICI is downloaded.
<div class="image-green-border">[[File:Translations Bulk Upload1.png|720px|Translations Bulk Upload1.png]]</div>
2. '''Open''' the downloaded Microsoft Excel file.

3. '''Click''' "Enable Editing". All ICI supported language Resource keys and their respective values are displayed.

4. '''Edit''' the ResouceKey of multiple languages as required.

5. '''Save''' the Excel file.

6. '''Click''' the "Upload File" button. The "Upload Translations" window opens.

7. '''Click "'''SelectFile". The "Open"''window opens.''

8. '''Select''' the updated Excel file.

9. '''Click''' "Open". A warning window opens indicating that this is a heavy operation and can potentially affect overall application performance.

10. '''Click''' "Ok". The "Upload Summary" displays the number ''of "''Records Uploaded", "Records Processed", and "Records Updated Successfully"''values.''

11. '''Click''' "Close". The label translations have been achieved for multiple languages in bulk.

== Data Management ==

Moving one step ahead in the self-service, ICI now allows performing data management activities for entities in all workflow stages.

The data management activities introduced with this release are update and delete operations for Agreements, Associated Documents, Contract Requests, User Information, Files and Attributes. These self-serve data management operations will empower administrative users to troubleshoot data inconsistency issues on their own.

However, users are advised to execute these operations cautiously as the data fix does not go through necessary business validations and are performed directly in the database itself. Furthermore, updating or deleting data through the data management tool cannot be undone and will not trigger any underlying rules, workflows, notifications, triggers, or integrations. Therefore, it is recommended to follow standard ICI workflows for any major or entity state modifications.
<div class="note-box">'''Note:''' The type of attributes such as Expressions, Conditional, Multi-select Lookup, Script, and System will remain non-editable and cannot be updated through the data management tool.</div>
By default, the Data Management utility is enabled and can be controlled through the technical configuration.

Administrators can perform the following actions from the Data Management page:

*Replace User
*Delete Entity
*Update Entity

A data management notification will be sent to a user who performs any data fix action along with primary owner, secondary owner and contract manager upon the data fix task completion with the details of the entity and modified data.

Please refer [[Notifications_Dashboard|"Notifications Dashboard"]] page for notification details.
<div class="note-box">'''Note:''' Data Management tools do not support updating data for any add-in applications. The validations will not be performed for any data fixed through Data Management tools.</div>
=== Replacing a user with multiple users ===

In ICI, administrators can replace user(s) with all associated records using the “Replace User” functionality. In practice, administrators may need to replace a user with more than one user. For example, if a user leaves the organization, the administrator may want to replace that user by dividing agreements associated with that user, in subsets, among multiple users. This would help the organization to balance the workload within its employees.

Administrators can now: 

*Replace the user with one or more users by selecting the entity and all/selective instances of that entity and create a saved search for an input to replace users.  
*Validate the replaced user role against the assigned role. 
*Get a notification on adding or completing a task.

This capability is available across ICI for contract requests, agreements, associations, masterdata, template and clause teams, user groups, and rules. A separate data management user interface is provided for these admin actions.
<div class="note-box">'''Note:''' Data Management tools do not support updating data for any add-in applications. The validations will not be performed for any data fixed through Data Management tools.</div>
To replace user:

1. '''Navigate''' to the "Data Management" page.

2. '''Select '''"Replace User" in the "Action" field. The fields to enter details such as user to be replaced, user to be assigned, replacement criteria, and entity are displayed.

3. '''Click '''Add User icon corresponding to the "Replace User" field. The "Search User" drawer opens.

[[File:Replace User1.png|720px]]<br/> ''' '''<br/> 4''. '''''Search '''and '''select '''a user you want to replace.
<div class="image-green-border">[[File:Select User1.png|720px|Select User.png]]</div> <div class="image-green-border"><br/> 5. '''Click '''"Add". The user will be entered in the "Replace User" field.</div>
6. '''Search '''and '''Add '''the "Assign To" user with whom you want to replace the user.

[[File:Assign Replace User.png|720px]]<br/>  <br/> 7. '''Select '''"Replace Based On" criteria from options:

*Saved Search
*Contract Type
*All Instances For Selected Entities 

'''Saved Search'''<br/> Administrators can replace a user in selective instances of an entity with different users by selecting a relevant Saved Search configured for that entity and user.

For example, user John Watson is added to the Teams of agreements from India and US regions. He can be replaced by multiple users by splitting agreements under his name in subsets using Saved Searches, one for agreements for the India region and the other for agreements in the US region. A saved search "JonhWatson_India_Agreements" can be created for John Watson's’s India region agreements and assigned to a user Johne Doel.  A saved search "JonhWatson_US_Agreements" for his US region agreements can be created and assigned to another user, for example, Prajakta.
<div class="note-box">'''Note: '''You can create "Saved Search" for Agreements from the Agreement Index page. Filter the records from "Refine View" in the left and "Save View". Then can update the view if required by selecting it under "More Views" in the title bar.</div>
7.1 '''Select '''"Saved Search". The "Entity" and "Saved Search" fields are displayed.

7.1.1 '''Select '''the Entity for which you want to replace the user in its instances "Team". For example, "Agreement Team".

7.1.2'''Select '''the "Saved Search". For example, "John_Watson_India_Agreements". Users need to create a saved search on the entity for which they want to replace a user in its instances team.

7.1.3 '''Click '''"Submit". The success message flashes displaying a "Replace User action is submitted successfully".
<div class="image-green-border">[[File:Saved Search1.png|720px|Saved Search.png]] </div> <div class="image-green-border">''' '''</div>
'''Contract Type'''<br/> This option replaces a user added in "Rules" actions configured on the selected "Contract Type" by the "Assign To" user.

7.2 '''Select '''"Contract Type". The "Entity" and "Contract Type" fields are displayed.

  7.2.1 '''Select '''the "Entity" as "Rules".

  7.2.2 '''Select '''"Contract Types". For example, "Standard Document Master".

  7.2.3 '''Click '''"Submit". The success message flashes displaying a "Replace User action is submitted successfully".
<div class="image-green-border">[[File:Contract Types Data Management.png|720px]]</div>
'''All Instances For Selected Entities'''

This option replaces a user in the Team of all instances of the selected entity by the "Assign To" user.

7.3 '''Select '''"All Instances For Selected Entities". The Entity field is displayed.

7.3.1 '''Select ''''Entity". For example, "Agreement Team". 

7.3.2 '''Click '''"Submit". The success message flashes displaying a "Replace User action is submitted successfully".

[[File:All Instances For Selected Entities.png|720px]]

The task is submitted and will be scheduled and processed according to the "Time zone" set in "User Preferences". The audit details are captured and displayed in the Agreement History tab.

Users can access the notifications in the "Data Management" category from the "Notifications Dashboard" from the bell icon on the top right. The notification contains a link to view the summary of the Replace User task. 

[[File:Data Management Notifications Dashboard1.png|600px]]

=== Deleting an Entity ===

When you want to remove certain records as a part of data clearance process, Administrators can mark the entity instances as deleted for you using Data Management tools.
<div class="note-box">Note: Deleting data this way, through data management tools, will not trigger any rules, events or integrations configured on concerned entities.</div>
When the entity instance is deleted, its linked child records will also be marked as deleted as per the standard behavior and will not be accessible. Administrators can delete instances of agreement, amendment, contract request and associated document entities in any workflow states.

To delete an entity instance:

1. '''Navigate '''to the "Data Management" option as mentioned in the above section.

2. '''Select '''the "Delete Entity" in the "Action" field. The fields to select an entity and its instance to be deleted, are displayed.
<div class="image-green-border">3. '''Select '''the "Entity" which you want to delete. For example, "Agreement".</div>
4. '''Click '''the Search icon corresponding to the "Entity Instance" field to select an instance of that entity to be deleted. The Lookup Search "Select Agreement" drawer for the selected entity opens.
<div class="image-green-border">[[File:Select Instance Entity1.png|720px|8.0-Data-fix-tools-Deleting.PNG]]</div>
5. '''Choose '''an instance and '''click "'''Select".

6. '''Click "'''Submit". The confirmation window appears'''.'''

7. '''Click '''"Yes". The selected entity instance will no longer be accessible.
<div class="note-box">'''Note: '''When you delete an entity instance, its linked associations will also be marked as deleted as per the standard behavior.</div>
=== Updating an Entity ===

There may be a business requirement to update selective data as a data maintenance and management process without processing any underlying actions associated with the update. Also, there may be a case, where a user does not have required access privileges to modify specific data. In such cases, Administrators can update data for you using Data Management tools.
<div class="note-box">'''Note:''' Updating data through data management tools will not trigger any rules, events, workflows or integrations configured on concerned entities.</div>
Administrators can update instances of agreement, amendment, contract request, associated document, masterdata, user information and commitment entities. Business users can view the data modifications done for a specific record in the audit logs from the History tab on the entity details page.

To update entity:

1. '''Navigate '''to the "Data Management" page as mentioned in the above section. 

2. '''Select '''the "Update Entity" option in the "Action" field. The fields to select an entity, its instance, and attribute are displayed.

3. '''Select "'''Entity". For example, "Masterdata".

4. '''Click '''the Search icon corresponding to the "Entity Instance" field to select an instance of the entity that you want to update. The Lookup Search "Select MasterData" drawer for the selected entity opens.

5. '''Select '''an instance. All supported attributes from the selected entity are displayed in the Attribute dropdown field.

6. '''Select '''the "Attribute" whose value you want to modify. For example, "Name". The attribute’s value from the selected instance is displayed for a user to edit.
<div class="image-green-border">7. '''Edit '''the attribute value as per the requirements. For example, enter a value for Name''.''</div> <div class="image-green-border">''[[File:Select Attribute.png|720px|Select Attribute.png]]''</div>
8. '''Click '''"Submit". The confirmation window opens.

9. '''Click '''"Yes" to proceed.
<div class="image-green-border">[[File:Submit Attribute Change.png|720px|Submit Attribute Change.png]]</div> <div class="image-green-border"> </div> <div class="image-green-border">The attribute of the entity instance will be updated with the new value.</div> <div class="image-green-border"> </div> <div class="note-box">'''Note:''' The Commitment attributes such as Commitment Code, Recurring Commitment, Commitment Frequency, Commitment type, Business Owner, Start Date and End date cannot be updated using Data Management actions.</div> <div><div><div> </div> <div id="_com_1">'''Related Topics: '''''<b>[[Agreement_Management|Agreement Management]] | [[Managing_Organization|Managing Organization]] | [[Managing_Users|Managing Users]] | [[Managing_User_Groups|Managing User Groups]] | [[Managing_Security_Groups|Managing Security Groups]] | [[Application_Settings|Application Settings]] | [[Notification_Settings|Notification Settings]] | [[Currencies|Currencies]] | [[Reasons|Reasons]] | [[Deleting_an_Agreement|Deleting an Agreement]] |[[Legacy_Upload|Legacy Upload ]]| [[Notifications_Dashboard|Notifications Dashboard]]</b>''</div> </div> </div>

File:Select Instance Entity1.png

2021-12-18T12:34:17Z

AR:

File:Data Management Notifications Dashboard1.png

2021-12-18T12:30:29Z

AR:

File:Data Management Notifications Dashboard.png

2021-12-18T12:28:13Z

AR:

File:All Instances For Selected Entities.png

2021-12-18T12:23:35Z

AR:

File:Contract Types Data Management.png

2021-12-18T12:18:28Z

AR:

File:Saved Search1.png

2021-12-18T12:13:41Z

AR:

File:Assign Replace User.png

2021-12-18T11:55:51Z

AR:

File:Select User1.png

2021-12-18T11:51:46Z

AR:

File:Replace User1.png

2021-12-18T11:49:32Z

AR:

Admin Task

2021-12-18T10:48:04Z

AR:

= Admin Task =

== Search Sync ==

The Search Sync tool gets data from Icertis Search for a given instance’s ''Sys Id'' and synchronizes it if required. Using the fetched ES value, the tool validates if the Sys Id is the latest for the respective instance or if a sync is required. The Administrator can access this option from the "Admin Task" on the "Admin" tile.

If the key exists, the latest value from ES will be displayed. If the key does not exist, the system displays an error message indicating that the value could not be fetched for the provided Sys Id. The Sys Id can be provided as input CSV file or as comma separated. Either comma separated Sys Ids can be entered or a CSV file can be uploaded.

This helps to make the entity search more streamlined and efficient. Users can quickly refer to related agreements at the time of deals or audits.
<div class="note-box">'''Note''': Data can be fetched from only one instance at a time. A dedicated key must exist for ES sync to work with "Sys ID".</div>
You can search the documents that an Agreement is linked to.

To use the Search Sync Tool:

1. '''Click''' Admin tile on the Home page and then '''click''' "Admin Task".
<div class="image-green-border">[[File:Admin Task Option1.png|720px|Search Sync 1]]</div> <div class="image-green-border"> </div> <div class="image-green-border">The Admin Task page opens</div>
2. '''Click''' "Search Sync"'' ''menu from the left pane.
<div class="image-green-border">[[File:Search Sync Menu2.png|720px]]</div> <div class="image-green-border"><div class="image-green-border">
3. '''Select''' the “Entity Type” from the drop-down to sync data to the Icertis Search. For example, Agreement.

4. '''Select''' the “Contract Type” from the drop-down''.''

To get the “Sys Ids”'','' you can either use the “Upload CSV” feature to upload the .CSV Agreement or enter the Sys Id using comma separated values in the box.

[[File:Entity Type1.png|720px|Entity Type.png]]
</div> </div>
5. '''Click''' the “Upload CSV” button to upload the CSV document. The “Upload Document” window opens.

6. '''Click''' the “Select File” button to upload a CSV file and add a note, if required.
<div class="image-green-border">[[File:UploadSysID File1.png|720px|Upload Sys ID File.png]]</div> <div class="image-green-border"> </div>
7. '''Click''' the "Upload" button. The file is uploaded to the "File Path" displayed''.''

''   '' If the uploaded file format is incorrect, an alert message is displayed. The supported file formats will be also be displayed.

[[File:Search Sync File Error1.png|720px]]

8. '''Click''' the "Sync" button. The "Sync Request Accepted" message is displayed. 
<div class="image-green-border">[[File:Search Sync Accepted.png|720px]]</div>
9. Users can now get data from ES for a given instance’s SysId and can check if it has the latest value or if sync is needed.

10. '''Select''' "Get ES Value".

11. Enter the SysId and '''click''' the "Go". If the key exists, the latest value from ES will be displayed. If the key does not exist, the error message "Please enter valid SysId" is displayed.
<div class="image-green-border">[[File:8.0-Search-Sync-GET-ES.PNG|720px|8.0-Search-Sync-GET-ES.PNG]]</div>
 
<div class="note-box">'''Note''': Data can be fetched from only one instance at a time.</div>
== Legacy Upload ==

Organizations may have a large number of existing Agreements that are created outside of ICI platform. These are henceforth referred to as Legacy Agreements. Organizations may want to import these Agreements to ICI to leverage its vast capabilities and manage all Agreements within a single platform.<br/> The Legacy Upload feature enables ICI Administrator to easily upload in bulk the legacy agreements that were created outside of ICI. This feature enhances productivity by allowing you to upload a large volume of existing Agreements and other entities using Excel.

The highlights of this feature are : 

*Uploading Agreements, Teams, Notes and Commitments in bulk.
*Uploading Associations, Masterdata, User Information and Amendments in bulk.
*Scheduled batch processing for improved performance.
*Enhanced validations, including the ability to exclude the specified attributes from being validated. 
*Ability to view logs and reporting of success and failure statuses for validations and uploads.

You can use the utility to upload the following entities: 

*Agreements 
*Amendments
*Associated Documents (with or without workflow)
*Masterdata (with or without workflow)
*Team, Notes, and Commitment
*User details

Refer to the  [[Legacy_Upload|Legacy Upload]] page or link for more details.

== Translations Editor ==
<div class="image-green-border">
The ICI platform is available in different languages and different languages label text are available for localization. However, to make any changes to the localization values, users had to reach out to the Solutions Engineering or Database teams. Sometimes, these changes were minor and of low complexity, but the turnaround time was substantial.

Hence, a self-service "Translations Editor" tool has been introduced that contains all strings that are localized.

Users can now download all keys and their localization values as an Excel file, modify multiple values, and upload the modified changes to ICI. Once the values are updated in ICI, the caches are updated automatically to avoid the cache flush and server restart. This has significantly enhanced productivity as the turnaround time to update the Resource Key values has been eradicated.

Using this tool, users can now:

*Search for a specific string using the search bar and update the Resource Key value for Language and Locale.
*Update multiple language strings by selecting and saving the Resource Key value.
*Download and upload the localization key values using Microsoft Excel.
*View the modified values in the ICI instance immediately.
</div>
To use the Translations Editor Tool:

1. C'''lick''' Admin tile on the Home page and then '''click''' "Admin Task". The "Admin Task" page opens.

2. '''Select''' the "Translation Editor"task from the left pane''.''

Users can update translations in the following ways:

*For selective editing, select a language and a resource key to update the translations.
*For bulk editing and updation of multiple languages and resource keys, use the Download / Upload option to download an MS Excel sheet.

===== Selective Editing to Update Translations =====

For editing Resource Key values selectively:

1. From the "Select Language" drop-down, select a language in which you want to edit the labels. For example, français (French).
<div class="image-green-border">[[File:Select Language1.png|720px|Select Language.png]]</div>
The Resource Key and respective values of the selected language are displayed.
<div class="image-green-border">[[File:Resource Key List1.png|720px|Resource Key List.png]]</div>
2. '''Ente'''r a "ResourceKey" value in the "Search" field to edit. For example, default. All ResourceKey(s) with the "Par défaut (default)" values from the French language are displayed.
<div class="note-box">'''Note:''' ResourceKey is a unique key by which the application gets its label text for different languages.</div>
3. '''Click '''the "Edit this Resource Key for the Multiple Languages"'' ''icon [[File:Edit Resource Key Icon.png|20px]] in the "Actions" column on the right.
<div class="image-green-border">
You can change the key for a single language or for multiple languages as required. For example, change "Par défaut to défaut" in French or "Predeterminado" in Español (Spanish) to "Defecto".

[[File:Edit Resource Key1.png|600px|Edit Resource Key.png]]

4. '''Click''' the "Update" button.

5. After the "Resources Updated Successfully" message is displayed.

You can select the respective languages (French or Spanish) to verify that the resources have been successfully updated.
</div>
===== Bulk Editing in Multiple Languages =====

 For editing Resource Key values of multiple languages in bulk:

1. '''Click''' the "Download File" button. A Microsoft Excel file (named BulkActionWorkBookStringResource) that contains all the Resource keys and values for all supported languages in ICI is downloaded.
<div class="image-green-border">[[File:Translations Bulk Upload1.png|720px]]</div>
2. '''Open''' the downloaded Microsoft Excel file.

3. '''Click''' "Enable Editing". All ICI supported language Resource keys and their respective values are displayed.

4. '''Edit''' the ResouceKey of multiple languages as required.

5. '''Save''' the Excel file.

6. '''Click''' the "Upload File" button. The "Upload Translations" window opens.

7. '''Click "'''SelectFile". The "Open"''window opens.''

8. '''Select''' the updated Excel file.

9. '''Click''' "Open". A warning window opens indicating that this is a heavy operation and can potentially affect overall application performance.

10. '''Click''' "Ok". The "Upload Summary" displays the number ''of "''Records Uploaded", "Records Processed", and "Records Updated Successfully"''values.''

11. '''Click''' "Close". The label translations have been achieved for multiple languages in bulk.

== Data Management ==

Moving one step ahead in the self-service, ICI now allows performing data management activities for entities in all workflow stages.

The data management activities introduced with this release are update and delete operations for Agreements, Associated Documents, Contract Requests, User Information, Files and Attributes. These self-serve data management operations will empower administrative users to troubleshoot data inconsistency issues on their own.

However, users are advised to execute these operations cautiously as the data fix does not go through necessary business validations and are performed directly in the database itself. Furthermore, updating or deleting data through the data management tool cannot be undone and will not trigger any underlying rules, workflows, notifications, triggers, or integrations. Therefore, it is recommended to follow standard ICI workflows for any major or entity state modifications.
<div class="note-box">'''Note:''' The type of attributes such as Expressions, Conditional, Multi-select Lookup, Script, and System will remain non-editable and cannot be updated through the data management tool.</div>
By default, the Data Management utility is enabled and can be controlled through the technical configuration.

Administrators can perform the following actions from the Data Management page:

*Replace User
*Delete Entity
*Update Entity

A data management notification will be sent to a user who performs any data fix action along with primary owner, secondary owner and contract manager upon the data fix task completion with the details of the entity and modified data.

Please refer [[Notifications_Dashboard|"Notifications Dashboard"]] page for notification details.
<div class="note-box">'''Note:''' Data Management tools do not support updating data for any add-in applications. The validations will not be performed for any data fixed through Data Management tools.</div>
=== Replacing a user with multiple users ===

In ICI, administrators can replace user(s) with all associated records using the “Replace User” functionality. In practice, administrators may need to replace a user with more than one user. For example, if a user leaves the organization, the administrator may want to replace that user by dividing agreements associated with that user, in subsets, among multiple users. This would help the organization to balance the workload within its employees.

Administrators can now: 

*Replace the user with one or more users by selecting the entity and all/selective instances of that entity and create a saved search for an input to replace users.  
*Validate the replaced user role against the assigned role. 
*Get a notification on adding or completing a task.

This capability is available across ICI for contract requests, agreements, associations, masterdata, template and clause teams, user groups, and rules. A separate data management user interface is provided for these admin actions.
<div class="note-box">'''Note:''' Data Management tools do not support updating data for any add-in applications. The validations will not be performed for any data fixed through Data Management tools.</div>
To replace user:

1. '''Navigate''' to the "Data Management" page.

2. '''Select '''"Replace User" in the "Action" field. The fields to enter details such as user to be replaced, user to be assigned, replacement criteria, and entity are displayed.
<div class="image-green-border">3. '''Click '''Add User icon corresponding to the "Replace User" field. The "Search User" drawer opens.</div> <div class="image-green-border">'' [[File:Replace User.png|720px|Replace User.png]]''<br/> ''' '''<br/> 4''. '''''Search '''and '''select '''a user you want to replace.</div> <div class="image-green-border">[[File:Select User.png|720px|Select User.png]]</div> <div class="image-green-border">''' '''<br/> 5. '''Click '''"Add". The user will be entered in the "Replace User" field.</div> <div class="image-green-border"> <br/> 6. '''Search '''and '''Add '''the "Assign To" user by whom you want to replace the user.</div> <div class="image-green-border">[[File:Assign User.png|720px|Assign User.png]]<br/>  <br/> 6. '''Select '''"Replace Based On" criteria from options:</div>
*Saved Search
*Contract Type
*All Instances For Selected Entities 
<div class="image-green-border">'''Saved Search'''<br/> Administrators can replace a user in selective instances of an entity with different users by selecting a relevant Saved Search configured for that entity and user.</div> <div class="image-green-border">For example, user John Watson is added to the Teams of agreements from India and US regions. He can be replaced by multiple users by splitting agreements under his name in subsets using Saved Searches, one for agreements for the India region and the other for agreements in the US region. A saved search "JonhWatson_India_Agreements" can be created for John Watson's’s India region agreements and assigned to a user Johne Doel.  A saved search "JonhWatson_US_Agreements" for his US region agreements can be created and assigned to another user, for example, Prajakta.</div> <div class="image-green-border"> </div> <div class="note-box">'''Note: '''You can create "Saved Search" for Agreements from the Agreement Index page. Filter the records from "Refine View" in the left and "Save View". Then can update the view if required by selecting it under "More Views" in the title bar.</div> <div class="image-green-border"> </div> <div class="image-green-border">[[File:8.0-Data-fix-tools6-John.PNG|720px|8.0-Data-fix-tools6-John.PNG]]<br/> ''' '''</div> <div class="image-green-border" style="margin-left: 40px;">6.1 '''Select '''"Saved Search". The "Entity" and "Saved Search" fields are displayed.</div> <div class="image-green-border" style="margin-left: 80px;"><br/> 6.1.1 '''Select '''the Entity for which you want to replace the user in its instances "Team". For example, "Agreement Team".<br/> 6.1.2 '''Select '''the "Saved Search". For example, "John_Watson_India_Agreements". Users need to create a saved search on the entity for which they want to replace a user in its instances team.</div> <div class="image-green-border" style="margin-left: 80px;">6.1.3 '''Click '''"Submit". The success toast message flashes displaying a "Replace User action is submitted successfully".</div> <div class="image-green-border">[[File:Saved Search.png|720px|Saved Search.png]] </div> <div class="image-green-border">''' '''</div> <div class="image-green-border">'''Contract Type'''<br/> This option replaces a user added in "Rules" actions configured on the selected "Contract Type" by the "Assign To" user.</div> <div class="image-green-border"> </div> <div class="image-green-border" style="margin-left: 40px;">6.2 '''Select '''"Contract Type". The "Entity" and "Contract Type" fields are displayed.</div> <div class="image-green-border" style="margin-left: 80px;">  6.2.1 '''Select '''the "Entity" as "Rules".</div> <div class="image-green-border" style="margin-left: 80px;">  6.2.2 '''Select '''"Contract Types". For example, "Statement of Work" and "ICM Master Services Agreement".</div> <div class="image-green-border" style="margin-left: 80px;">  6.2.3 '''Click '''"Submit". The success toast message flashes displaying a "Replace User action is submitted successfully".</div> <div class="image-green-border" style="margin-left: 80px;"> </div> <div class="image-green-border">[[File:8.0-Data-fix-tools8.PNG|720px|8.0-Data-fix-tools8.PNG]]</div> <div class="image-green-border"> </div> <div class="image-green-border">'''All Instances For Selected Entities'''</div> <div class="image-green-border"> </div> <div class="image-green-border">This option replaces a user in the Team of all instances of the selected entity by the "Assign To" user.</div> <div class="image-green-border" style="margin-left: 40px;"><br/> 6.3 '''Select '''"All Instances For Selected Entities". The Entity field is displayed.</div> <div class="image-green-border" style="margin-left: 80px;">6.3.1 '''Select ''''Entity". For example, "Agreement Team". </div> <div class="image-green-border" style="margin-left: 80px;">6.3.2 '''Click '''"Submit". The success toast message flashes displaying a "Replace User action is submitted successfully".</div> <div class="image-green-border" style="margin-left: 80px;"> </div> <div class="image-green-border">'''''[[File:8.0-Data-fix-tools9.PNG|720px|8.0-Data-fix-tools9.PNG]]'''''</div> <div class="image-green-border">'' ''</div> <div class="image-green-border">The task is submitted and will be scheduled and processed according to the "Time zone" set in "User Preferences".</div> <div class="image-green-border">The audit details are captured and displayed in the Agreement History tab.</div> <div class="image-green-border">'' ''</div> <div class="image-green-border">Users can access the notifications in the "Data Management" category from the "Notifications Dashboard" from the bell icon on the top right.</div> <div class="image-green-border">The notification contains a link to view the summary of the Replace User task. </div> <div class="image-green-border"> </div> <div class="image-green-border">[[File:8.0-Data-fix-tools10.PNG|720px|8.0-Data-fix-tools10.PNG]]</div> <div class="image-green-border"> </div>
=== Deleting an Entity ===

When you want to remove certain records as a part of data clearance process, Administrators can mark the entity instances as deleted for you using Data Management tools.
<div class="note-box">Note: Deleting data this way, through data management tools, will not trigger any rules, events or integrations configured on concerned entities.</div>
When the entity instance is deleted, its linked child records will also be marked as deleted as per the standard behavior and will not be accessible. Administrators can delete instances of agreement, amendment, contract request and associated document entities in any workflow states.

To delete an entity instance:

1. '''Navigate '''to the "Data Management" option as mentioned in the above section.

2. '''Select '''the "Delete Entity" in the "Action" field. The fields to select an entity and its instance to be deleted, are displayed.
<div class="image-green-border">3. '''Select '''the "Entity" which you want to delete. For example, "Agreement".</div>
4. '''Click '''the Search icon corresponding to the "Entity Instance" field to select an instance of that entity to be deleted. The Lookup Search "Select Agreement" drawer for the selected entity opens.

5. '''Choose '''an instance and '''click "'''Select".
<div class="image-green-border">[[File:Select Instance Entity.png|720px|8.0-Data-fix-tools-Deleting.PNG]]</div>
6. '''Click "'''Submit". The confirmation window appears'''.'''

7. '''Click '''"Yes". The selected entity instance will no longer be accessible.
<div class="note-box">'''Note: '''When you delete an entity instance, its linked associations will also be marked as deleted as per the standard behavior.</div> <div class="image-green-border">[[File:8.0-Data-fix-tools-Deleting1.PNG|720px|8.0-Data-fix-tools-Deleting1.PNG]]</div>
=== Updating an Entity ===

There may be a business requirement to update selective data as a data maintenance and management process without processing any underlying actions associated with the update. Also, there may be a case, where a user does not have required access privileges to modify specific data. In such cases, Administrators can update data for you using Data Management tools.
<div class="note-box">Note: Updating data through data management tools will not trigger any rules, events, workflows or integrations configured on concerned entities.</div>
Administrators can update instances of agreement, amendment, contract request, associated document, masterdata, user information and commitment entities. Business users can view the data modifications done for a specific record in the audit logs from the History tab on the entity details page.

To update entity:

1. '''Navigate '''to the "Data Management" page as mentioned in the above section. 

2. '''Select '''the "Update Entity" option in the "Action" field. The fields to select an entity, its instance, and attribute are displayed.

3. '''Select "'''Entity". For example, "Masterdata".

4. '''Click '''the Search icon corresponding to the "Entity Instance" field to select an instance of the entity that you want to update. The Lookup Search "Select MasterData" drawer for the selected entity opens.

5. '''Select '''an instance.
<div class="image-green-border">All supported attributes from the selected entity are displayed in the Attribute dropdown field.</div> <div class="image-green-border">[[File:Select MasterData Instance.png|720px|Select MasterData Instance.png]]</div>
6. '''Select '''the "Attribute" whose value you want to modify. For example, "Name". The attribute’s value from the selected instance is displayed for a user to edit.
<div class="image-green-border">7. '''Edit '''the attribute value as per the requirements. For example, enter a value for Name''.''</div> <div class="image-green-border">''[[File:Select Attribute.png|720px|Select Attribute.png]]''</div>
8. '''Click '''"Submit". The confirmation window opens.

9. '''Click '''"Yes" to proceed.
<div class="image-green-border">[[File:Submit Attribute Change.png|720px|Submit Attribute Change.png]]</div> <div class="image-green-border"> </div> <div class="image-green-border">The attribute of the entity instance will be updated with the new value.</div> <div class="image-green-border"> </div> <div class="note-box">'''Note:''' The Commitment attributes such as Commitment Code, Recurring Commitment, Commitment Frequency, Commitment type, Business Owner, Start Date and End date cannot be updated using Data Management actions.</div> <div><div><div> </div> <div id="_com_1">'''Related Topics: '''''<b>[[Agreement_Management|Agreement Management]] | [[Managing_Organization|Managing Organization]] | [[Managing_Users|Managing Users]] | [[Managing_User_Groups|Managing User Groups]] | [[Managing_Security_Groups|Managing Security Groups]] | [[Application_Settings|Application Settings]] | [[Notification_Settings|Notification Settings]] | [[Currencies|Currencies]] | [[Reasons|Reasons]] | [[Deleting_an_Agreement|Deleting an Agreement]] |[[Legacy_Upload|Legacy Upload ]]| [[Notifications_Dashboard|Notifications Dashboard]]</b>''</div> </div> </div>

File:Translations Bulk Upload1.png

2021-12-18T10:45:15Z

AR:

File:Edit Resource Key1.png

2021-12-18T10:41:46Z

AR:

File:Edit Resource Key Icon.png

2021-12-18T10:37:14Z

AR:

File:Resource Key List1.png

2021-12-18T10:33:40Z

AR:

File:Select Language1.png

2021-12-18T10:30:32Z

AR:

File:Search Sync Accepted.png

2021-12-18T10:18:15Z

AR:

File:Search Sync File Error1.png

2021-12-18T10:13:57Z

AR:

File:Search Sync File Error.png

2021-12-18T10:11:49Z

AR:

File:UploadSysID File1.png

2021-12-18T10:08:14Z

AR:

File:Entity Type1.png

2021-12-18T10:04:07Z

AR:

File:Search Sync Menu2.png

2021-12-18T09:50:29Z

AR:

File:Search Sync Menu1.png

2021-12-18T09:46:58Z

AR:

File:Admin Task Option1.png

2021-12-18T09:45:09Z

AR:

Generate a Report

2021-12-18T09:39:22Z

AR:

= Generate a Report =

<font face="Segoe UI">Using the Reports feature you can generate various types of reports.</font>

=== <font face="Segoe UI">'''To generate a Report:'''</font> ===
<div class="image-green-border">1. '''Click''' the "Reports" tile on the "Home" page.</div> <div class="image-green-border"> </div> <div class="image-green-border">[[File:Generate a Report1.png|720px|Generate a Report1.png]]</div>
The Reports page opens. You can view all the default and custom report templates.
<div class="image-green-border">2. '''Select''' an option from the "Defaults Reports" drop-down menu. You can view "All", "Legal" & "Compliance", "Workflow" or "Admin" Reports''.''</div> <div class="image-green-border"> </div> <div class="image-green-border">[[File:Default Reports1.png|300px|Default Reports.png]]</div> <div class="image-green-border"> </div> <div class="image-green-border">The Reports will be displayed depending on the category you select.</div> <div class="image-green-border"> </div> <div class="image-green-border">3.  '''Click''' the tile for the type of report you need to generate.</div> <div class="image-green-border"> </div> <div class="image-green-border">[[File:Report Type1.png|450px|Report Type.png]]</div>
 The report for the selected tile appears on a new tab. For example, selecting the Agreement Clause Content Report opens the report in a new tab displaying filters for the report.
<div class="image-green-border">5. Select the required filters and '''click''' the "View Report" button.</div> <div class="image-green-border">[[File:View Report1.png|720px|View Report.png]]</div> <div class="image-green-border"> </div> <div class="image-green-border">6.  Based on the combination of selected filters, the report is displayed with appropriate columns.</div> <div class="image-green-border">[[File:Report Filters1.png|720px|Report Filters.png]]</div> <div class="image-green-border"> </div> <div class="note-box">'''Note:''' If you do not select a filter or apply incorrect filters, you see a message that filter parameters cannot be blank.</div>
<font face="Segoe UI">You can now export the report into Excel, CSV, or PDF.</font>
<div class="image-green-border"><font face="Segoe UI">[[File:Reports Export1.png|720px|Reports Export.png]]</font></div>

Generate a Report

2021-12-18T09:34:45Z

AR:

= Generate a Report =

<font face="Segoe UI">Using the Reports feature you can generate various types of reports.</font>

=== <font face="Segoe UI">'''To generate a Report:'''</font> ===
<div class="image-green-border">1. '''Click''' the "Reports" tile on the "Home" page.</div> <div class="image-green-border"> </div> <div class="image-green-border">[[File:Generate a Report1.png|720px]]</div>
The Reports page opens. You can view all the default and custom report templates.
<div class="image-green-border">2. '''Select''' an option from the "Defaults Reports" drop-down menu. You can view "All", "Legal" & "Compliance", "Workflow" or "Admin"Reports''.''</div> <div class="image-green-border"> </div> <div class="image-green-border">[[File:Default Reports1.png|300px|Default Reports.png]]</div> <div class="image-green-border"> </div> <div class="image-green-border">The Reports will be displayed depending on the category you select.</div> <div class="image-green-border"> </div> <div class="image-green-border">3.  '''Click''' the tile for the type of report you need to generate.</div> <div class="image-green-border"> </div> <div class="image-green-border">[[File:Report Type1.png|450px|Report Type.png]]</div>
 The report for the selected tile appears on a new tab. For example, selecting the Agreement Clause Content Report opens the report in a new tab displaying filters for the report.
<div class="image-green-border">5. Select the required filters and '''click''' the "View Report" button.</div> <div class="image-green-border">[[File:View Report1.png|720px|View Report.png]]</div> <div class="image-green-border"> </div> <div class="image-green-border">6.  Based on the combination of selected filters, the report is displayed with appropriate columns.</div> <div class="image-green-border">[[File:Report Filters1.png|720px|Report Filters.png]]</div> <div class="image-green-border"> </div> <div class="note-box">'''Note:''' If you do not select a filter or apply incorrect filters, you see a message that filter parameters cannot be blank.</div>
<font face="Segoe UI">You can now export the report into Excel, CSV, or PDF.</font>
<div class="image-green-border"><font face="Segoe UI">[[File:Reports Export1.png|720px|Reports Export.png]]</font></div>

File:Reports Export1.png

2021-12-18T09:33:29Z

AR:

File:Report Filters1.png

2021-12-18T09:31:22Z

AR:

File:View Report1.png

2021-12-18T09:29:26Z

AR:

File:Report Type1.png

2021-12-18T09:27:32Z

AR:

File:Default Reports1.png

2021-12-18T09:25:08Z

AR:

File:Generate a Report1.png

2021-12-18T09:22:42Z

AR:

Rule

2021-12-17T10:26:49Z

AR:

= Rule =

You can work with Rules in several ways. 

== Create a Rule ==

You can create rules to create Requests or Agreements using the Rules menu under the Configure tile. For example, you can create a Rule for an Agreement to get the Supporting Documents auto attached at a predefined state. Only users provided with administrative privileges can create Rules.

Using Rules you can ensure that:

* The Agreements/Contracts contain appropriate data depending on the type
* The Agreements/Contracts get executed as required

With ICI, you can create Rules for Contract Types. You can create various types of Rules only for the published Contract Types.

To create a Rule:

1. '''Click''' "Configure" tile on the Home page.

2. '''Click''' the "Rules" menu under the Configure tile. The Rules page opens.
<div class="image-green-border">[[File:Configure Rules.png|720px]]</div>
3. '''Click''' the "Create" button on the Rules page. The Create Rule page opens.

The Create Rule page contains the following  tabs:

*Setup
*Build

Let us understand each tab one by one.

=== Setup ===

1. '''Select''' the "Contract Type" for which you want to create a Rule in the "Contract Type" drop-down list.

2. '''Type''' a name of the rule in the "Rule Name" box.

3. '''Type''' a description for the rule in the "Rule Description" box.

4. '''Select''' the type of the rule in the "Rule Type"'' ''from the "Rule Type" drop-down list. 
<div class="image-green-border">[[File:Create Rule New.png|500px]]</div>
For each type of a Rule, you need to select an approver role from the drop-down list.

*Approval Rule : To build a Rule that defines the conditions in which a specific user will be the approver for the Agreement.

:If you select the Rule Type as "Approval Rule", the "Team Role" field is displayed. You can configure multiple approval rule sets, thus enabling greater flexibility in creating approval rules.<br/> '''Select''' the appropriate role of an approver from the following list of team roles:
<ul style="margin-left: 40px;">
<li>Approver</li>
<li>Deviation Approver</li>
<li>External Signatory</li>
<li>Internal Signatory</li>
<li>Reviewer</li>
</ul>
<div class="image-green-border" style="margin-left: 40px;">[[File:Approval Rule.png|450px]]</div>
*Clause Assembly: To build a Rule that defines the conditions in which a specific clause will open in an Agreement.
*Contract Type Selection: To build a Rule that defines the conditions in which a specific contract type will be selected while creating an Agreement.
*Dynamic Association: To build a Rule that defines the conditions in which a specific Agreement/Associated Document will be selected while creating an Agreement.
*Dynamic Attribute: To build a Rule that defines the conditions in which a specific attribute will open while creating an Agreement.
*Set Attribute Value: Define the value of the attribute.
*Template Selection: To build a Rule that defines the conditions in which a specific template will be selected while creating an Agreement.
<div class="image-green-border" style="margin-left: 40px;">[[File:Rule Types.png|400px]]</div> <div class="note-box">'''Note''': The types of rules that are displayed in the list vary according to the type of the contract you select in the ''Contract Type'' list.</div>
5. '''Click''' "Next". The Build tab opens.

=== Build ===

The Build tab has the following two panes:

*Build: You can add a Rule in this pane.
*Eavluate: You can type the information that is used to evaluate the Rule you create.

To add a Rule:

1. '''Click''' "Add Rule".

2. Under Conditions, '''select''' the appropriate condition:

:
:*And: All the conditions have to be fulfilled to satisfy the rule.
:*Or: One of the conditions have to be fulfilled to satisfy the rule.

3. Next to the icon, in the "Select Value" field, select the appropriate attribute from the list provided:

:
:*Parent Contract Type
:*Priority
:*Priority Inheritance
:*Simba Reference ID
:*Status
:*Status Changed Date
:*Template Name
:*Type Of Paper

 4. Based on the attribute you have selected, select appropriate value in the very next "Select Value" field from the list provided:

:
:*Contains
:*Equals
:*Not Equals
:*Starts With
:*Greater Than
:*Greater Than or Equals
:*Less Than
:*Less Than or Equals
:*Not Equals
:*Subset Of: the Rule is satisfied where the user wants a Rule to be executed only if the entity field contains a subset of the configured values. This operator is applicable for multi select lookup that supports evaluation of string, number, user, percentage and email data types only. For better understanding, please refer to the subsequent section on Subset Of operator.
:*Has No Value: the Rule is satisfied when no value is selected for the attribute. For example, if the ''Contract value'' is 0, then the Agreement is automatically put on hold (or cancelled).
:*Has A Value: the Rule is satisfied as long as the attribute has some value. This includes all Data Types and system-defined Attributes such that Rules can be set up for an Attribute having any value. For example, you want to set up a Rule so that an Approver John Doe should approve the Contract if a discount is applicable to it, irrespective of the value of the discount. Then, user can add a Rule using the Has A Value condition such that John Doe is added as an Approver if the discount has a value of 5%, 10% or whatever value is desired. 
:*Not Contains: the Rule is satisfied when the value of an attribute is blank. For example, if the ''City'' value is blank, a Rule will be triggered, which will default the name of the city to the city of the head office.

Once selected, '''enter''' an appropriate value in the "Enter Value" field.

5. '''Click''' the Add icon to add a condition.

6. '''Click''' "Add Condition" button to add another group of conditions. When you add a group, all the conditions in the group should be fulfilled to satisfy the rule.

7. Under "Actions", in the "Select Action" list, select the desired action.

:For example:
:*Require Approval From All
:*Require Approval From Any
:*Select User From Attribute

8. '''Select''' actions consequent to the conditions you have set, and then enter their value. For example, under "Conditions", if you select "Created By Equals x User", then under "Actions" you may select "Require Approval From Any", and then type appropriate value. that is if the user x creates an Agreement using the selected Contract Type, then it will require approval from any of the selected approvers.

9. '''Type''' the number of approvers required in the "Minimum Approvers" text box, and then '''type''' appropriate "Step Number" for those Approvers. The Agreement approval process flows sequentially according to the Step Number of the approver. When Approvers are defined based on the user attribute, the Administrator can specify a minimum number of approvals required for an Agreement before it can move to the next step in the workflow. As a result, not all Approvers configured for the specific user attribute are required to approve the Agreement.
<div class="image-green-border">[[File:Create Rule Conditions.png|720px]]<br/>  </div>
=== Evaluate ===

Based on the "Contract Type" you select in the "Setup" section, relevant attributes are displayed in the "Evaluate" pane. The information you type in this pane evaluates the Rule that you create.

'''Click''' ''Next''. The ''Summary'' tab opens.

=== Has A Value Condition ===

The Has A Value condition has been enhanced to include all Data Types and system-defined Attributes such that Rules can be set up for an Attribute having any value.

Let's apply ''Has A Value ''condition on ''Agreement Code'' Attribute of  Contract Type ''Teaming Agreement'' having ''Auto ''Data Type. 

1. '''Click''' "Configure" tile on the Home page.

2. '''Click''' the "Rules" menu under the Configure tile. The Rules page opens.

3. '''Select''' the "Contract Type" from the "Contract Type" drop-down list.

4. '''Type''' a name of the rule in the "Rule Name" box.

5. '''Type''' a description for the rule in the "Rule Description" box.

6. '''Select''' the type of the rule in the "Rule Type"'' ''from the "Rule Type" drop-down list. For example, Approval Rule.

7.  '''Select '''the role for team member from the "Team Role" drop-down list. For example, Approver.
<div class="image-green-border">[[File:Approval Rule.png|450px]]</div>
7.  '''Click '''"Next". The Build tab of Create Rule page opens.

8.  '''Select '''the "Attribute" value (system or user defined) for which you want to apply the condition from the ''Select Value'' drop-down list. For example, Agreement Code.

9.  '''Select '''the "Has A Value" condition from the Operators drop-down list.

10.  '''Select''' the action that you want to take from the "Actions"''drop-down list. For example, Require Approval From All. 

11.  '''Select '''a user from the "Select User" drop-down list.

12.  '''Select '''a corresponding "Step Number" for the selected User.

13.  '''Click '''"Add Action" if you want to add another condition.

14.  '''Select''' "Stop Processing More Rules" checkbox.
<div class="note-box">'''Note:''' The Stop Processing More Rules option when set to Yes allows you to stop evaluating further Rules for the Ruleset.</div>
17.  '''Click '''the "Evaluate" button to evaluate the Rule. For example, enter code in the Agreement Code field as per the defined Rule.
<div class="image-green-border">[[File:Evaluate Rules.png|550px]]</div> <div class="image-green-border">18.  '''Click '''the "Evaluate"''button on the Evaluate Rules pane to evaluate the Rule you created. The Rule Validation Summary window opens.<br/> [[File:Rule Evaluation Results.png|300px]]</div>
=== Subset Of Operator ===

With a Subset''of'' operator, user can configure conditions for power sets (i.e. cases where the user wants a Rule to be executed only if the entity field contains a subset of the configured values). This new operator, ''Subset of'', which is applicable to only multiselect lookup supports evaluation of string, number, user, percentage and email data types only. Let's consider an example to define a ''Template Selection'' Rule with the ''Subset Of ''operator using ''Number'' Data Type.

1. '''Click''' "Configure" tile on the Home page.

2. '''Click''' the "Rules" menu under the Configure tile. The Rules page opens.

3. '''Select''' the "Contract Type" from the "Contract Type" drop-down list.

4. '''Type''' a name of the rule in the "Rule Name" box.

5. '''Type''' a description for the rule in the "Rule Description" box.

6. '''Select''' the type of the rule in the "Rule Type"'' ''from the "Rule Type" drop-down list.

7.  '''Select '''the role for team member from the "Team Role" drop-down list.

8.  '''Click '''"Next". The Build tab'' ''opens''.''

9.''  '''''Click '''"Add Rule" in the Build'' ''tab.

*'''Select '''the Contract Type from the drop-down list, which helps you to select the Attribute set for which you want to create the Rule. For example, ''Teaming Agreement''.
*'''Select '''the Multi-Select Lookup Attribute for which you want to apply the condition from the Select Value drop-down list. For example, RAP_Supplier Name. RAP_Supplier Name is an Attribute of Teaming Agreement with Number Data Type having Is Multi Select flag enabled.
*'''Select ''"'''''VALUE"''condition from the drop-down list. 
*'''Select''' the "Subset of Operator" from the drop-down list. 
*'''Select''' the options where you want to apply the ''Subset Of'' operator. For example, Mac & Jhonson and RAP_Supplier1. This means the Template Selection Rule will only trigger when a RAP_Supplier Name field has either of Mac & Jhonson and RAP_Supplier1 or both names.  
<div class="note-box">'''Note: '''The Subset Of operator is available only for the Multi Select Lookup Attribute.</div>
10.  '''Select '''the Action that you want to take from the "Actions" drop-down list. For example, Select Template. 

11.  '''Select '''the Template to be available when the defined conditions are met. For example, Template approval verification and Clause assembly verification perf.

12.  '''Select''' the "Stop Processing More Rules" checkbox.
<div class="note-box">'''Note:''' The Stop Processing More Rules option when setting to ''Yes'' allows you to stop evaluating further Rules for the Ruleset. </div>
13.  '''Click '''the "Evaluate" button to evaluate the Rule. 

14.  '''Enter''' the required value as per the defined Rule. For example, '''enter''' Mac & Jhonson and RAP_Supplier1 in the RAP_Supplier Name field.

15.  '''Click '''the "Evaluate" button on the Evalute Rules pane. The Rules Evaluation Results window opens.
<div class="note-box">'''Note''': For mutually exclusive rules, you now have an option to stop processing subsequent rules.</div>
=== Creating Count Based Rules ===

ICI allows you to set the Rules based on the total number of selected values (count of selected values) in multi-select type Attributes.

'''''<span style="color:#FF0000;">For example, for an attribute Country Name, if the user selects more than two countries i.e. Count is Greater Than 2, then the Agreement can be sent for approval to the selected users. <could not locate the Count option for attribute "Country Name"></span>'''''
<div class="image-green-border">[[File:Count based rules 1.png|720px|RTENOTITLE]]</div>
The supported operators are: Contains, Not Contains, Equals, Not Equals, Starts With, Has a Value, and Has No Value, 

[[File:Rules Operators List.png|200px]]

== Using Masterdata Value options in Rules Actions ==

You can define Rules based on the Masterdata in the following ways:

*You can define Rules on Masterdata columns when lookup to the Masterdata is added as an Agreement Attribute. You can configure the list of Lookup and/or Cascade Attributes as conditions for Agreement or Contract Request Contract Types Rules, thus improving flexibility in Rules. For example, you may have a supplier Masterdata being referred in MSA Agreement Type via Supplier Country Name lookup. But, there may be scenarios where Rules are required to be configured on basis of Supplier City Name and is not available as an Attribute in the Agreement, which is now made possible.
*ICI also supports Masterdata value options in the Actions section of Rules, so that you can define Rules without having the Cascade Attribute on the Contract Type where the Rule is being written. For example, if multiple signatories are part of a Lookup Masterdata record, we can now define the Rule (such as – Select User From Attribute) on the Masterdata record itself and use them in the Rule directly, instead of defining Cascade Lookup Attributes in the Agreement. This drastically reduces the time and effort to create and maintain a large number of Attributes for Agreement Contract Types.
<div class="image-green-border">[[File:Master Agreement Rule.png|720px]]</div>
=== Create Rules for Multi-party Agreements ===

Rules can be written for individual attributes of an Association (as done for parent Contract Types). All attributes for Associations are available for the given Rule conditions. You can search selected values on an Agreement or an Associated Document. Depending on the type of the attribute, standard operators are applicable. For example, ''Contains, Starts With, Equals, Greater Than'', and so on.

Rules can also accommodate the count of the Associations so that you can add Clauses based on the count of the Associations. If you ''Select All'' or ''Select Any'', there is no need to specify the count of the Associations to satisfy the rule. However, when selecting the option ''Select Count'', you need to specify the number of Associations, irrespective of the attribute value, that should meet the condition and satisfy the Rule. This rule applies to any type of Association, parent/child or peer.

However, if the attribute belongs to an Association, the following additional filter Conditions are available for all the Rules:

*''Select All'': If all the Associations satisfy the condition
*''Select Any'': If any Association satisfies the condition
*''Select Count'': If the number of Associations specified satisfy the condition
<div class="image-green-border">[[File:Multiparty-Rules1.PNG|760px|Multiparty Rules]]</div>
For a multi-division Agreement, you can write Rules based on individual instances of the multi-value attributes.

Rules can accommodate the count of the Associations, besides ''Select All'' and ''Select Any ''Conditions. If you ''Select All'' or ''Select Any'', there is no need to specify the count of the Associations to satisfy the Rule. However, when you ''Select Count'', then you need to specify the number of Associations, irrespective of the attribute value, that should meet the condition and satisfy the Rule.
<div class="image-green-border">[[File:Multiparty-Rules2.PNG|760px|Multiparty Rules - Select Count]]</div>
If you have more than two Associations, the values of the attributes are irrelevant. The count of the Association takes precedence.

== Changes in Document Assembly will replace tags with Metadata value ==

When Rules are written based on the Attributes of the Association, the Rules support tagging of the Metadata that belongs to the Association. The Associations may either be parent-child or peer. After the content control tag is entered, the value of the associated instances’ metadata is placed in the content control as shown in the example below.

'''Example:'''

1. The saved search for the Agreement is sorted based on the Agreement Code.

2. After the content control tag is entered, the value of the associated instances metadata is placed in the content control.

3. If the value taken from the Agreement above was ''Acme Inc''. for the first instance, then it will be displayed as shown in the figure after Edit or Publish.
<div class="image-green-border">[[File:Rules - Changes in Document Assembly.png|250px|Create a Rule - Changes in Document Assembly will replace tags with metadata value]]</div>
== View or Edit a Rule ==

In ICI, you can View, Edit, Copy, Activate, Deactivate, or Lock a Rule. Follow these steps to View or Edit a Rule:

1. '''Click''' "Configure" tile on the Home page.

2. '''Click''' the "Rules" menu under the Configure tile. The Rules page opens.

3. '''Select''' the appropriate Contract Type from the "Select Contract Type" drop-down list. A list of Rules that are created for the selected Contract Type is displayed. You can use the filters provided in each column to find the desired Rule.

4. '''Select''' the check box next to the Rule name, and then '''click''' the "Delete" button to delete the Rule. You can also select multiple rules, and '''click''' the "Delete Rules".
<div class="image-green-border">[[File:Select Rule Contract Type.png|720px]]</div>
You can also perform the following actions on a particular rule:
<div class="image-green-border">[[File:Rules Operations.png|720px]]</div>
*Activate/Deactivate icon''': '''To activate or deactivate a Rule. The Rule will no more be applicable to the associated Contract Type.
*Edit: To edit the selected Rule. On the Edit Rule page, edit the appropriate information. and '''click '''Update. Editing the Rule automatically locks it. When updating the Rule, there is a checkbox option (default – unchecked) on the Edit Rule page, indicating that the Rule will be unlocked on update. If checked, the Rule stays locked for the other users. After editing the Rule, you can evaluate and later Save & Close it in order to lock the rule.
*Copy: To copy the selected Rule for another Contract Type. In the ''Copy Rule'' dialog box, '''select''' Contract Type, '''type''' the Rule name and then '''click''' ''Copy''. The Rule becomes applicable for another Contract Type that you selected.
*View: To view the details of the selected Rule. The Rule Summary page opens where you can view the Rule details of the selected Rule.
*Audit Log: To view the Audit Logs of the Rule. Audit Logs screen contains the complete history of the specific Rule. Here, you can track all the changes made to the Rules, including the deletion. Editing a rule set inside a Rule creates a hyperlink Hide/Show All Changes next to that log. '''Click''' the hyperlink to see the Old and New values.
*Lock Rule: This icon indicates that the Ruleset is available for editing. '''Click '''to lock a Rule or a Ruleset, so that other users can not edit the Rule until you unlock it. 
*Unlock Rule: This icon indicates that the Ruleset is locked. When a user hovers over the icon the name of the user who has locked the Rule is displayed.

== Create a Contract Type Selection Rule ==

When you are creating an Agreement from a Contract Request, the Contract Type Selection rule defines which Contract Type should be selected'''.'''

With ICI, you can create Rules for Contract Types. You can create various types of Rules only for the published Contract Types.

To create a Contract Type Selection Rule:

1. '''Click''' "Configure" tile on the Home page.

2. '''Click''' the "Rules" menu under the Configure tile. The Rules page opens.

3. '''Click''' "Create" on the Rules page.

The Create Rule page consists of the following tabs:

*Setup
*Build

Let us understand each tab one by one.

=== Setup ===

4. '''Select''' the "Contract Type" from the "Contract Type" drop-down list.

5. '''Type''' a name of the rule in the "Rule Name" box.

6. '''Type''' a description for the rule in the "Rule Description" box.

7. '''Select''' the type of the rule in the "Rule Type"'' ''from the "Rule Type" drop-down list.

8.  '''Select '''the role for team member from the "Team Role" drop-down list.
<div class="note-box">'''Note''': The types of Rules that are displayed in the list vary according to the type of Contract you select in the ''Contract Type ''list. </div>
9. '''Click''' "Next". The Build tab opens.
<div class="image-green-border">[[File:Create Rule.png|400px]]</div>
=== Build ===

The Build tab has the following  panes:

*Build: You can add a rule in this pane.
*Evaluate: You can type the information that is used to evaluate the rule you create.

To add a Rule:

1. '''Click''' "Add Rule".

2. Under "Conditions", select from the following options:

*And: All the conditions have to fulfilled to satisfy the Rule.
*Or: One of the conditions have to be fulfilled to satisfy the Rule.

 3. In the "Select Value" drop-down list next to the icon, select an attribute. Based on the attribute you have selected, select the appropriate value. For example, you have selected "Created By" as an attribute, you have to select an operator such as Equals or Not Equals. Then, type the appropriate value in the text box says Mr. Someone.

4. '''Click''' the "Add Contition" button to add another condition. When you add a group, all the conditions in the group should be fulfilled to satisfy the Rule.

'''Evaluate'''

Based on the Contract Type you select in the Setup tab, relevant attributes are displayed in the Evaluate pane. The information you type in this pane evaluates the Rule that you create. Rule evaluation results are displayed after you '''click''' the "Evaluate" button

== Create a Template Selection Rule ==

You can select Templates to use them in the agreement creation process. Using Template Selection Rules, you can specify which Templates should appear under specific conditions. The Templates appear in the ''Templates'' tab in the Agreement Creation process.

You can create multiple sets of Template Selection Rules allowing you to manage similar Rules with ease.

To create a Template Selection Rule:

1. '''Click''' "Configure" tile on the Home page.

2. '''Click''' the "Rules" menu under the Configure tile. The Rules page opens.

3. '''Click''' "Create" on the Rules page. The Create Rule page.

The Create Rule page consists of the following tabs:

*Setup
*Build

=== Setup ===

1. '''Select''' the "Contract Type" from the "Contract Type" drop-down list.

2. '''Type''' a name of the rule in the "Rule Name" box.

3. '''Type''' a description for the rule in the "Rule Description" box.

4. '''Select''' the type of the rule in the "Rule Type"'' ''from the "Rule Type" drop-down list.

5.  '''Select '''the role for team member from the "Team Role" drop-down list.

6. '''Click''' "Next". The Build tab opens.

=== ''' '''Build ===
<div class="image-green-border">
The Build tab has the following  panes:

*Build: You can add a rule in this pane.
*Evaluate: You can type the information that is used to evaluate the rule you create.
</div>
1. '''Click''' "Add Rule".

2. Under "Conditions", select from the following :

*And: All the conditions have to be fulfilled to satisfy the Rule.
*Or: One of the conditions have to be fulfilled to satisfy the Rule.

3. In the "Select Value" drop-down list next to the icon, select a condition. Based on the condition you have selected, select the subsequent effect in the next drop-down list. For example, you have selected "Contract Type Name", then you can select from Contains, Equals, Not Equals, and Starts With. Then, '''type''' the appropriate value in the text box say (name of the Contract Type).

4. '''Click''' the "Add"'' ''icon to add another condition.

5.  '''Click '''the "Add Group" icon to add a group of conditions. When you add a group, all the conditions in the group should be fulfilled to satisfy the Rule.

6. Under "Actions", in the "Select Action" list, '''click''' "Select Template", and then '''click''' the Add icon to select appropriate Template.

7. '''Click''' "Select Template By Condition" under "Actions" to select a Template based on certain metadata such as Created By, Created On, and Effective From.

The "Stop Processing More Rules" option within a Ruleset allows you to stop evaluating further Rules for the Ruleset, if you enable this option.
<div class="image-green-border">[[File:Template Selection Rule.png|720px]]</div> <div class="note-box">Note: Once multiple Template Selection Rules are defined, ICI executes these Rules sequentially.</div>
=== Evaluate ===

1. '''Click '''the "Evaluate"'' ''button. Based on the Contract Type you selected in the Setup tab, relevant attributes appear in this tab. You can type information that is relevant to the Rule(s) you just specified.

2. In the Evaluate Rules page, c'''lick '''the "Evaluate" button to validate the Rule that you created. You can also see the preview of the selected Template and Template Variables values.

3. '''Click''' "Validate". The validation summary is displayed.

== Creating an Approval Rule ==

In the Approval Rule, you can define conditions in which a certain user will be the Approver of an Agreement.<br/> You can create the Approval Rule for:

*Agreements
*Clauses
*Templates

To create an Approval Rule:

1. '''Click''' "Configure" tile on the Home page.

2. '''Click''' the "Rules" menu under the Configure tile. The Rules page opens.

3. '''Click''' "Create" on the Rules page. The Create Rule page.

The Create Rule page consists of the following tabs:

*Setup
*Build

=== Setup ===

1. '''Select''' the "Contract Type" from the "Contract Type" drop-down list.

2. '''Type''' a name of the rule in the "Rule Name" box.

3. '''Type''' a description for the rule in the "Rule Description" box.

4. '''Select''' the "Approval Rule"''' i'''n the Rule Type list. The "Team Role" field is displayed.

5. '''Select''' the appropriate role of an approver from the following list of roles:

:
::
::*Approver
::*Deviation Approver
::*External Signatory
::*Internal Signatory
::*Reviewer
<div class="note-box">'''Note''': Types of rules that appear in the list vary according to the selected Contract Type. </div>
6. '''Click''' "Next". The "Build" tab appears.

=== Build ===

The Build tab has the following  panes:

*Build: You can add a rule in this pane.
*Evaluate: You can type the information that is used to evaluate the rule you create.

'''Builder'''<br/> Follow the procedure below to add an Approval Rule:

1. '''Click''' "Add Rule".

2. Under "Conditions", select from the following :

*And: All the conditions have to be fulfilled to satisfy the Rule.
*Or: One of the conditions have to be fulfilled to satisfy the Rule.

3. In the "Select Value" drop-down list, select an attribute. Based on the attribute you have selected, select the appropriate value. For example, under "Conditions", you have selected Contract Type Name. Now, you have to select from Contains, Equals, Not Equals, and Starts With. Then, type the appropriate value in the text box, say MSA.

4. '''Click''' "Add" icon to add another condition.

5. '''Click '''the''' "'''Add Group" icon to add another group of conditions. When you add a group, all the conditions in the group should be fulfilled to satisfy the rule.

6. Under "Actions", in the "Select Action" list, select from the following actions.

*Require Approval From All
*Require Approval From Any 
*Require Approval From All By Condition
*Require Approval From Any By Condition
*Select User From Attribute

7. '''Select''' actions consequent to the conditions you have set, and then type their value.

:For example, under "Conditions", if you select "Created By Equals x User", then under "Actions" you may select "Require Approval From Any", and then type the appropriate value. If the user x creates agreement using the selected contract type, then it will require approval from any of the selected approvers.

8. '''Type''' the number of approvers required in the "Minimum Approvers" text box, and then '''type''' the appropriate "Step Number" for those approvers. The Agreement approval process flows sequentially according to the ''Step Number'' of the approver.

=== Evaluate ===

1. '''Click '''the "Evaluate"'' ''button. Based on the Contract Type you selected in the Setup tab, relevant attributes appear in this tab. You can type information that is relevant to the Rule(s) you just specified.

2. In the Evaluate Rules page, c'''lick '''the "Evaluate" button to validate the Rule that you created. You can also see the preview of the selected Template and Template Variables values.

3. '''Click''' "Validate". The validation summary is displayed.

== Create a Dynamic Attribute Rule ==

In the Dynamic Attribute rule, you can define conditions in which a certain attribute appears while creating an Agreement.

To create a dynamic attribute rule:

1. '''Click''' "Configure" tile on the Home page.

2. '''Click''' the "Rules" menu under the Configure tile. The Rules page opens.

3. '''Click''' "Create" on the Rules page. The Create Rule page.

The Create Rule page consists of the following tabs:

*Setup
*Build

=== Setup ===

1. '''Select''' the "Contract Type" from the "Contract Type" drop-down list.

2. '''Type''' a name of the rule in the "Rule Name" box.

3. '''Type''' a description for the rule in the "Rule Description" box.

4. '''Select''' Dynamic Attribute from the "Rule Type" list'''.'''
<div class="note-box">'''Note''': The types of rules that appear in the list vary according to the type of the contract you select in the ''Contract Type'' list.</div>
6. '''Click''' "Next". The "Build" tab appears.

=== Build ===

The Build tab has the following  panes:

*Build: You can add a rule in this pane.
*Evaluate: You can type the information that is used to evaluate the rule you create.

1. '''Click''' "Add Rule".

2. Under "Conditions", select from the following :

*And: All the conditions have to be fulfilled to satisfy the Rule.
*Or: One of the conditions have to be fulfilled to satisfy the Rule.

3. In the "Select Value" drop-down list, select an attribute. Based on the attribute you have selected, select the appropriate value. For example, under "Conditions", you have selected Created By, you have to select from ''Equals'' and ''Not Equals''. Then '''type''' the appropriate value in the text box.. 

4. '''Click''' "Add" icon to add another condition.

5. '''Click '''the''' "'''Add Group" icon to add another group of conditions. When you add a group, all the conditions in the group should be fulfilled to satisfy the rule.

6. Under "Actions", '''click''' in the box next to "Select Attribute" to select attribute(s) that you want to be selected by default (while creating a request/contract/agreement).that is if Mr. Someone is creating a request/contract/agreement, then A, B, C attributes should be displayed in ICI.

=== Evaluate ===

1. '''Click '''the "Evaluate"'' ''button. Based on the Contract Type you selected in the Setup tab, relevant attributes appear in this tab. You can type information that is relevant to the Rule(s) you just specified.

2. In the Evaluate Rules page, c'''lick '''the "Evaluate" button to validate the Rule that you created. You can also see the preview of the selected Template and Template Variables values.

3. '''Click''' "Validate". The validation summary is displayed.

== Create a Dynamic Association Rule ==

The Dynamic Association Rule enables you to associate supporting documents for a particular Contract Type.

To create a dynamic association rule:

1. '''Click''' "Configure" tile on the Home page.

2. '''Click''' the "Rules" menu under the Configure tile. The Rules page opens.

3. '''Click''' "Create" on the Rules page. The Create Rule page.

The Create Rule page consists of the following tabs:

*Setup
*Build

=== Setup ===

1. '''Select''' the "Contract Type" from the "Contract Type" drop-down list.

2. '''Type''' a name of the rule in the "Rule Name" box.

3. '''Type''' a description for the rule in the "Rule Description" box.

4. '''Select''' Contract Type Selection''' '''in the "Rule Type" list.
<div class="note-box">'''Note''': The types of rules that appear in the list vary according to the type of the contract you select in the ''Contract Type ''list. </div>
6. '''Click''' "Next". The "Build" tab appears.

=== Build ===
<div class="image-green-border"> </div> <div class="image-green-border">1. '''Click''' "Add Rule".</div> <div class="image-green-border">
2. Under "Conditions", select from the following :

*And: All the conditions have to be fulfilled to satisfy the Rule.
*Or: One of the conditions have to be fulfilled to satisfy the Rule.
</div>
3. In the "Select Value" drop-down list next to the icon, select an attribute. Based on the attribute you have selected, select the appropriate value. For example, you have selected Created By as an attribute, you have to select from Equals and Not Equals, and then, '''type''' the appropriate value in the text box.

4. '''Click''' the "Add Action" button to add another condition.

5. '''Click''' the "Add Group" button to add another group of conditions. When you add a group, all the conditions in the group should be fulfilled to satisfy the Rule.

6. '''Click''' the icon next to Select Association under "Actions"'' ''to select the Contract Type that you want to be selected by default (while creating an Agreement from a Request) that is  if a request is created by any user, then while creating an Agreement from the Request, the given Contract Type will be selected by default.
<div class="image-green-border">[[File:Dynamic Association.png|720px]]</div>
=== Evaluate ===

1. '''Click '''the "Evaluate"'' ''button. Based on the Contract Type you selected in the Setup tab, relevant attributes appear in this tab. You can type information that is relevant to the Rule(s) you just specified.

2. In the Evaluate Rules page, c'''lick '''the "Evaluate" button to validate the Rule that you created. You can also see the preview of the selected Template and Template Variables values.

3. '''Click''' "Validate". The validation summary is displayed.

== Create an Event Rule ==

With ICI, you can define an Event Rule for a Contract Request, Agreement, and an Associated Document. The Event Rule helps you to setup a condition that triggers when that particular event occurs. You can define an Event Rule for an entity at different stages such as create, send for approval, approve, update, delegate, and so on.

An administrator can now: 

*Create multiple rulesets for event rules for any entity per event
*Copy event rules to target entity. However, a new rule is created for the target entity and it does not override the existing one, if any. The name of the ruleset remains unique throughout the system

For example, you can create multiple rulesets for event rules for any entity.

When multiple Event rules are defined, ICI ensures all event rules are executed.

To create an Event Rule:

1. '''Click''' "Configure" tile on the Home page.

2. '''Click''' the "Rules" menu under the Configure tile. The Rules page opens.

3. '''Click''' "Create" on the Rules page. The Create Rule page.

The Create Rule page consists of the following tabs:

*Setup
*Build

=== Setup ===

1. '''Select''' the "Contract Type" from the "Contract Type" drop-down list.

2. '''Type''' a name of the rule in the "Rule Name" box.

3. '''Type''' a description for the rule in the "Rule Description" box.

4. '''Select''' the Event Rule in the "Rule Type" list.
<div class="image-green-border">5. '''Select''' an appropriate category in the Event list.<br/> [[File:Create Event Rule.png|500px]]</div> <div class="note-box">'''Note''': Types of ''Events ''that appear in the list vary according to the type of Entity you select in the ''Contract Type list. ''</div>
6. '''Click''' "Next". The "Build" tab appears.

=== Build ===

The Build tab has the following  panes:

*Build: You can add a rule in this pane.
*Evaluate: You can type the information that is used to evaluate the rule you create.

1. '''Click''' "Add Rule".

2. Under "Conditions", select from the following :

*And: All the conditions have to be fulfilled to satisfy the Rule.
*Or: One of the conditions have to be fulfilled to satisfy the Rule.

3. '''Select''' an appropriate attribute value in the "Select Value" list. Based on your selection the value field is populated.

For example: In the "Select Value" list, if you '''select''' Created By, then you can select value as either Equals or Not Equals. '''Click '''the Select User icon to add a new user.

 4. '''Click '''the "Add Action" button to add another condition.

5. '''Click '''the "Add Group" button to add another group of conditions. When you add a group, all the conditions in the group should be fulfilled to satisfy the Rule.

6. Under Actions, in the "Select Action" list, select from following the list of actions.

*Add to Team
*Set Attribute Value
*Select User From Attribute
<div class="note-box">'''Note''': When creating an Event rule for an Agreement, on selecting the Agreement Add Association'' ''event, the Actions'' ''field includes a Copy Attribute Values field. Using this field, you can copy the attribute value from an Associated Document to that Agreement attribute. Selecting the''' '''Copy Attribute Values field displays the Associated Document Name, Parent Attribute Name, and the Association Attribute Name fields. '''Select''' the appropriate attributes. </div> <div class="image-green-border"> </div> <div class="image-green-border">[[File:Cav.jpeg|720px|RTENOTITLE]]</div>
=== Add to Team ===

Add to Team condition is addition of users to a team after the particular event occurs. For example, addition of approvers after the Agreement Created event occurs.
<div class="image-green-border">[[File:Add to Team.png|720px]]</div>
1. '''Select''' an appropriate user role from the "User Role" list
<div class="image-green-border">[[File:Add Role.png|400px]]</div>
'''2. Click''' the "Add User" icon. The Select User window opens.
<div class="image-green-border">[[File:Select a User.png|300px]]</div>
3. In the Select User window, '''select''' the relevant user, and then '''click''' "Add".
<div class="image-green-border">[[File:Select User Drawer.png|720px]]</div>
'''Set Attribute Value'''

Set Attribute Value condition is setting an attribute value that appears after the particular event occurs.

'''Select '''"Set Attribute Value" from the "Actions" drop-down list. The Set Attribute Value pane opens, in this pane you can set a specific attribute value for that event. For example, you can regulate an event for a specific organization unit by selecting an appropriate organization department. This ensures that only those department users will have access to the event.

In the "Organization Unit" box, '''click '''the Search icon. The Select Organization Unit window opens. '''Select''' a "Department" and '''click''' "OK".
<div class="image-green-border">[[File:Set Attribute Value.png|600px]]</div>
'''Select User From Attribute'''

'''Select''' User From Attribute condition is addition of users from the user attributes. For example, addition of approvers from the attribute Modified By after the Agreement Created event occurs.

'''Select''' an appropriate user role from the "User Role" list, and then '''select '''an appropriate category in the "UserTypeAttribute" list.

=== Evaluate ===

1. '''Click '''the "Evaluate"'' ''button. Based on the Contract Type you selected in the Setup tab, relevant attributes appear in this tab. You can type information that is relevant to the Rule(s) you just specified.

2. In the Evaluate Rules page, c'''lick '''the "Evaluate" button to validate the Rule that you created. You can also see the preview of the selected Template and Template Variables values.

3. '''Click''' "Validate". The validation summary is displayed.

== Create a Contract Admin Rule ==

In the ICI, you can create various types of Rules for various Contract Types. Rules can only be created for published Contract Types.<br/> In the Contract Admin Rule, you can define a Contract Admin user through any of the user attributes of that Contract Request, by using the ''Select User From Attribute ''option. This provides more flexibility in identifying the Contract Admin user who creates Agreement based on the Contract Request.

To create a Contract Admin Rule:

1. '''Click''' "Configure" tile on the Home page.

2. '''Click''' the "Rules" menu under the Configure tile. The Rules page opens.

3. '''Click''' "Create" on the Rules page. The Create Rule page.

The Create Rule page consists of the following tabs:

*Setup
*Build

=== Setup ===

1. '''Select''' the "Contract Type" from the "Contract Type" drop-down list.

2. '''Type''' a name of the rule in the "Rule Name" box.

3. '''Type''' a description for the rule in the "Rule Description" box.

4.  '''Select''' Approval Rule''' '''in the "Rule Type" list.

5. '''Select''' Contract Admin in the "Team Role" list.
<div class="image-green-border">[[File:Contract Admin.png|400px]]</div> <div class="note-box">'''Note''': The type of rules that appear in the list vary according to the type of the Contract you select in the ''Contract Type ''list. </div>
6. '''Click''' "Next". The "Build" tab appears.

=== Build ===

The Build tab has the following  panes:

*Build: You can add a rule in this pane.
*Evaluate: You can type the information that is used to evaluate the rule you create.

To add a rule:

1. '''Click''' "Add Rule".

2. Under "Conditions", select from the following :

*And: All the conditions have to be fulfilled to satisfy the Rule.
*Or: One of the conditions have to be fulfilled to satisfy the Rule.

3. In the ''Select Value'' drop-down list next to the icon, select an attribute. Based on the attribute you have selected, select the appropriate value. For example, you have selected ''Created By'' as an attribute, you have to select from ''Equals'' and ''Not Equals''. Then, '''type''' the appropriate value in the text box.

4. '''Click''' the Add icon to add another condition.

5. '''Click '''the ''Add Group'' icon to add another group of conditions. When you add a group, all the conditions in the group should be fulfilled to satisfy the Rule.

6. '''Click''' the icon next to Select Contract Type''' '''under "Actions" to select the contract type that you want to be selected by default (while creating an Agreement from Request).that is  if a request is created by any user, then while creating an Agreement from the Request, the given Contract Type will be selected by default.

=== Evaluate ===

1. '''Click '''the "Evaluate"'' ''button. Based on the Contract Type you selected in the Setup tab, relevant attributes appear in this tab. You can type information that is relevant to the Rule(s) you just specified.

2. In the Evaluate Rules page, c'''lick '''the "Evaluate" button to validate the Rule that you created. You can also see the preview of the selected Template and Template Variables values.

3. '''Click''' "Validate". The validation summary is displayed.

== Create a Notification Rule ==

Notifications are sent to the users added in a Team. However, they may sometimes be sent to users who are not a part of the conventional team. To do this, a Rule must be created and to do so, a subscription must be added.

Users can also send the notification emails to the email addresses captured while creating an agreement instance by configuring a Notification rule. Users can also set the email type for the notifications sent.

'''To create a Notification Rule:'''

1. '''Click''' "Configure" tile on the Home page.

2. '''Click''' the "Rules" menu under the Configure tile. The Rules page opens.

3. '''Click''' "Create" on the Rules page. The Create Rule page.

The Create Rule page consists of the following tabs:

*Setup
*Build

=== Setup ===

1. '''Select''' the "Contract Type" from the "Contract Type" drop-down list.

2. '''Type''' a name of the rule in the "Rule Name" box.

3. '''Type''' a description for the rule in the "Rule Description" box.

4. '''Select '''a rule type form the "Rule Type". For example, Notification Rule. The Subscriptions field is displayed.

5. '''Select '''the subscription. For example, Email Type configuration.
<div class="image-green-border">[[File:Notification Rule.png|400px]]</div>
6. '''Click''' "Next". The "Build" tab appears.

7. On the Build tab,''' ''''''click '''the ''"Add Rule"'' button. The section to add rule conditions opens.

8. '''Select '''email type in the "Select Action" field in the "''Actions"'' section. For example, Add Recipient (BCC:).

To add users provisioned in the system:

9. '''Click '''the "Search User" icon to select a user. The Search User window opens.

10. '''Select '''a user, and click "Add". For example, ICI Admin. The user is added to the rule.

To add user emails captured during runtime while creating the agreement instance:

11. '''Select '''"Attributes". For example, Observer Emails.

12. '''Disable '''the "Stop Processing More Rules" field. The further evaluation of Rules within a Ruleset continues.

13. '''Click '''"Evaluate". The page to evaluate the rule by entering attributes values of the selected Contract Type''opens.

14. '''Click '''"Evaluate" on the Evaluate Rule pane. The rule summary is displayed.

15. '''Click '''''"''Save & Close". The Rule created successfully message appears.

The notification will be sent to the user upon satisfying the rule conditions.

== Create a Mandatory Association Rule ==

In a mandatory Association rule, you can define certain conditions to evaluate whether any associations are mandatory for an agreement.

To create a Mandatory Associations rule:

1. '''Click''' "Configure" tile on the Home page.

2. '''Click''' the "Rules" menu under the Configure tile. The Rules page opens.

3. '''Click''' "Create" on the Rules page. The Create Rule page.

The Create Rule page consists of the following tabs:

*Setup
*Build

=== Setup ===

1. '''Select''' the "Contract Type" from the "Contract Type" drop-down list.

2. '''Type''' a name of the rule in the "Rule Name" box.

3. '''Type''' a description for the rule in the "Rule Description" box.

4. '''Select''' Mandatory Association from the "Rule Type" list.

6. '''Click''' "Next". The "Build" tab appears.

=== Build ===

The Build tab has the following  panes:

*Build: You can add a rule in this pane.
*Evaluate: You can type the information that is used to evaluate the rule you create.

To add a rule:

1. '''Click''' "Add Rule".

2. Under "Conditions", select from the following :

*And: All the conditions have to be fulfilled to satisfy the Rule.
*Or: One of the conditions have to be fulfilled to satisfy the Rule.

3. In the ''Select Value'' drop-down list next to the icon, select an attribute. Based on the attribute you have selected, select the appropriate value. For example, you have selected ''Created By'' as an attribute, you have to select from ''Equals'' and ''Not Equals''. Then, '''type''' the appropriate value in the text box.

4. '''Click''' the Add icon to add another condition.

5. '''Click '''the ''Add Group'' icon to add another group of conditions. When you add a group, all the conditions in the group should be fulfilled to satisfy the Rule.

6. '''Click''' the icon next to Select Contract Type''' '''under "Actions" to select the contract type that you want to be selected by default (while creating an Agreement from Request).that is  if a request is created by any user, then while creating an Agreement from the Request, the given Contract Type will be selected by default.

=== Evaluate ===

1. '''Click '''the "Evaluate"'' ''button. Based on the Contract Type you selected in the Setup tab, relevant attributes appear in this tab. You can type information that is relevant to the Rule(s) you just specified.

2. In the Evaluate Rules page, c'''lick '''the "Evaluate" button to validate the Rule that you created. You can also see the preview of the selected Template and Template Variables values.

3. '''Click''' "Validate". The validation summary is displayed.

== Create an Auto-attachment Rule ==

Users can configure the ''Event Rule'' for agreements and amendments to attach standard documents automatically when certain actions such as ''Create, Publish'' and ''Update ''occur. The rule is configured using association name and standard document's saved search.

To configure an event rule for agreement:

1. '''Click''' "Configure" tile on the Home page.

2. '''Click''' the "Rules" menu under the Configure tile. The Rules page opens.

3. '''Click''' "Create" on the Rules page. The Create Rule page.

The Create Rule page consists of the following tabs:

*Setup
*Build

=== Setup ===

1. '''Select''' the "Contract Type" from the "Contract Type" drop-down list.

2. '''Type''' a name of the rule in the "Rule Name" box.

3. '''Type''' a description for the rule in the "Rule Description" box.

4. '''Select '''Event Rule''in the "Rule Type"''field.

5. '''Select '''type of event in "Event"''field. For example, Agreement Updated''.''
<div class="image-green-border">[[File:Auto Attachment Rule.png|500px]]</div>
6. '''Click '''Next. The Build tab opens.

=== Build ===

The Build tab has the following  panes:

*Build: You can add a rule in this pane.
*Evaluate: You can type the information that is used to evaluate the rule you create.

To add a rule:

1. '''Click''' "Add Rule".

2. Under "Conditions", select from the following :

*And: All the conditions have to be fulfilled to satisfy the Rule.
*Or: One of the conditions have to be fulfilled to satisfy the Rule.

3. '''Select '''Additional Actions for Associations in first drop-down in Actions field.

4. '''Select '''CreateAssociatedDocumentInstancesEventHook in next drop-down.
<div class="note-box">Note: The option CreateAssociatedDocumentInstancesEventHook is enabled through technical configuration.</div>
5. '''Select '''the ''Associated Document Contract Type'' from which you want to auto-attach the documents in next drop-down.
<div class="note-box">Note: ''Associated Document Contract Types'' that are in a parent-child relationship with the selected ''Agreement Contract Type'' will only be available in the drop-down. Also the ''Associated Document Contract Types'' which have document assembly and mandatory attributes will not be available.</div>
6. '''Select '''the saved search name in the next drop-down. For example, SearchAutoAttachment''.''

7. '''Disable '''the "Stop Processing More Rules" field. The further evaluation of rules within a ruleset continues.
<div class="image-green-border">[[File:Auto-attachment Rule.png|720px]]</div> <div class="image-green-border"> </div>
=== Evaluate ===

1. '''Click '''the "Evaluate"'' ''button. Based on the Contract Type you selected in the Setup tab, relevant attributes appear in this tab. You can type information that is relevant to the Rule(s) you just specified.

2. In the Evaluate Rules page, c'''lick '''the "Evaluate" button to validate the Rule that you created. You can also see the preview of the selected Template and Template Variables values.

3. '''Click''' "Validate". The validation summary is displayed.

== Create a Clause Assembly Rule ==

The Agreement Templates use Clauses. Clauses can be manually added to the Agreement Template or a Clause Assembly Rule can be created to add all the relevant clauses to the Templates.

You can create multiple sets of Clause Assembly Rules allowing you to manage similar Rules with ease.

To create a Clause Assembly Rule:

1. '''Click''' "Configure" tile on the Home page.

2. '''Click''' the "Rules" menu under the Configure tile. The Rules page opens.

3. '''Click''' "Create" on the Rules page. The Create Rule page.

The Create Rule page consists of the following tabs:

*Setup
*Build

=== Setup ===

1. '''Select''' the "Contract Type" from the "Contract Type" drop-down list.

2. '''Type''' a name of the rule in the "Rule Name" box.

3. '''Type''' a description for the rule in the "Rule Description" box.

4. '''Select''' Clause Assembly''' '''in the "Rule Type" list.

5. '''Click''' Next to go to the Build tab.

=== Build ===

The Build tab has the following  panes:

*Build: You can add a rule in this pane.
*Evaluate: You can type the information that is used to evaluate the rule you create.

To add a rule:

1. '''Click''' "Add Rule".

2. Under "Conditions", select from the following :

*And: All the conditions have to be fulfilled to satisfy the Rule.
*Or: One of the conditions have to be fulfilled to satisfy the Rule.

3. In the ''Select Value'' drop-down list next to , select a condition. Based on the condition you have selected, select the subsequent effect in the next drop-down list. For example, you have selected ''Contract Type Name'', then you can select from ''Contains'', ''Equals'', ''Not Equals'', and ''Starts With''. Then, '''type''' the appropriate value in the text box say (name of the Contract Type).

4. '''Click '''to add another condition.

5. '''Click '''to add a group of conditions. When you add a group, all the conditions in the group should be fulfilled to satisfy the Rule.

6. Under ''Actions'', in the ''Select Action'' list, '''click''' ''Select Clause'', and then '''click '''to select appropriate clause. For example, for the selected Contract type, if the Annual Revenue Equals 300000, then (this is the condition) the Action is Select the ''Deviation Analysis Clause''.

7. The ''Stop Processing More Rules'' option within a Ruleset allows you to stop evaluating further Rules for the Ruleset, if you select ''Yes'' for this option.
<div class="note-box">'''Note''': Once multiple Template Selection Rules are defined, ICI executes these Rules sequentially. </div>
=== Evaluate ===

1. '''Click '''the "Evaluate"'' ''button. Based on the Contract Type you selected in the Setup tab, relevant attributes appear in this tab. You can type information that is relevant to the Rule(s) you just specified.

2. In the Evaluate Rules page, c'''lick '''the "Evaluate" button to validate the Rule that you created. You can also see the preview of the selected Template and Template Variables values. For example, find the Attribute (Annual Revenue, in this case) that you had entered in the Rule ''Builder'', insert the same value there (30000).

3. '''Click''' "Validate". The validation summary is displayed.

== Create an Extension Selection Rule ==

Users have the flexibility to use attributes of masterdata as extensions to any agreement or associated document. These extended attributes can be selected and added when user is actually creating the instance. This considerably improves usability and simplifies the process for users who deal with hundreds of items and need to have multiple configurations.<br/> <br/> Users now:

*Can create rules to attach masterdata attributes (single or multiple) to your associated documents and agreements based on certain conditions
*Have flexibility to select (add or remove) and use any masterdata attributes as extensions at the time of agreements/associated documents creation

=== Configuring Extension Rules for Agreements and Associated Documents ===

Users need to create an Extension Selection Rule Type on Contract Types.<br/> <br/> To create Extension Selection Rule Type for Agreements and Associated Documents:

1. '''Click''' "Configure" tile on the Home page.

2. '''Click''' the "Rules" menu under the Configure tile. The Rules page opens.

3. '''Click''' "Create" on the Rules page. The Create Rule page.

The Create Rule page consists of the following tabs:

*Setup
*Build

=== Setup ===

1. '''Select''' the "Contract Type" from the "Contract Type" drop-down list.

2. '''Type''' a name of the rule in the "Rule Name" box.

3. '''Type''' a description for the rule in the "Rule Description" box.

4. '''Select''' Extension Selection in the "Rule Type" drop-down list. 
<div class="image-green-border">[[File:Extension Selection Rule.png|500px]]<br/>  <br/> 5. '''Click''' Next to go to the Build tab.</div> <div class="image-green-border"> </div> <div class="image-green-border">
=== Build ===

The Build tab has the following  panes:

*Build: You can add a rule in this pane.
*Evaluate: You can type the information that is used to evaluate the rule you create.

To add a rule:

1. '''Click''' "Add Rule".

2. Under "Conditions", select from the following :

*And: All the conditions have to be fulfilled to satisfy the Rule.
*Or: One of the conditions have to be fulfilled to satisfy the Rule.

3. '''Select''' the required value from the "Select Value" drop-down list.

4. '''Select''' the Equals condition from the next drop-down list.  

5. '''Select''' the Test from the next drop-down list.
</div> <div class="note-box">'''Note''': The ''Extension Selection'' Rule Type has two actions<br/> * ''Select Extension Contract Types'': all attributes of selected Masterdata Contract Types are available when creating an agreement/associated document. * ''Select Extension Attributes'': selected attributes of the Masterdata Contract Types are available when creating an agreement/associated document. * Select Extension Attribute Groups: selected attributes group of the Masterdata Contract Types are available when creating an agreement/associated document.</div>
6. '''Select''' Select Extension Contract types from the "Actions" drop-down list. 

7. '''Click''' the (+) icon to add the attributes of all contract type. For example, Product or Service Master.

[[File:Extension Add Rule.png|720px]]<br/> <br/> Similarly, create additional rules as follows:

*Action: "Select Extension Attributes" with contract type attribute as "FoodPurchaseMaster" with attribute values "Food Category", "Expiry Date", and "Quantity"
*Action: "Select Extension Attribute Groups" with contract type attribute as "FoodMaster" with attribute value "Quality" 

=== Evaluate ===

1. '''Click '''the "Evaluate"'' ''button. Based on the Contract Type you selected in the Setup tab, relevant attributes appear in this tab. You can type information that is relevant to the Rule(s) you just specified.

2. In the Evaluate Rules page, c'''lick '''the "Evaluate" button to validate the Rule that you created. You can also see the preview of the selected Template and Template Variables values. For example, find the Attribute (Annual Revenue, in this case) that you had entered in the Rule ''Builder'', insert the same value there (30000).

3. '''Click''' "Validate". The validation summary is displayed.
<div class="image-green-border">4. '''Click '''''"''Save & Close". The Information''window opens indicating that the rule created successfully. </div>
We have created an ''Extension Selection'' Rule Type using the attributes of ''PurchaseMaster, Food Master ''and ''FoodPurchaseMaster ''Masterdata Contract Types.

For more information, see ''Creating Agreement and Associated Document instances with flexible entity attributes'' 

'''Related Topics: '''[[Agreement_Management|Agreement Management]] '''| ''' [[Configuration|Configuration]] | [[Template_Management|Template Management]] | [[Clause_Management|Clause Management]] | 

File:Extension Add Rule.png

2021-12-17T10:15:34Z

AR:

File:Extension Selection Rule.png

2021-12-17T10:04:41Z

AR:

File:Auto-attachment Rule.png

2021-12-17T09:56:12Z

AR:

File:Auto Attachment Rule.png

2021-12-17T09:48:46Z

AR:

File:Notification Rule.png

2021-12-17T09:32:42Z

AR:

File:Contract Admin.png

2021-12-17T09:25:47Z

AR:

File:Set Attribute Value.png

2021-12-17T09:17:34Z

AR:

File:Select User Drawer.png

2021-12-17T09:13:00Z

AR:

File:Select a User.png

2021-12-17T09:11:11Z

AR:

File:Add Role.png

2021-12-17T09:08:12Z

AR:

File:Add to Team.png

2021-12-17T09:03:37Z

AR:

File:Create Event Rule.png

2021-12-17T08:44:46Z

AR:

File:Dynamic Association.png

2021-12-17T08:33:54Z

AR:

File:Template Selection Rule.png

2021-12-17T08:01:24Z

AR:

File:Rules Operations.png

2021-12-17T07:11:14Z

AR: