From ICIHelp7.16
Jump to: navigation, search

Bulk Actions 

Users can perform bulk actions using the Bulk Actions tile on the Home page to create and update multiple entities directly within ICI. When uploaded, these entities become part of the ICI workflow and can be managed within ICI itself. You can also perform these actions using Excel Add-in. With this utility, the overhead of installing and updating ICI Excel Add-in periodically on your machine can be avoided, besides, reducing the time taken to create and/or update records in ICI.

Bulk Actions

Using Bulk Action you can:

  • Create new Agreements and Masterdata
  • Update existing Amendments and Agreements.
  • Create/update Associations with Agreements or Amendments.
  • Process multiple batches in parallel, instead of sequentially processing them.
  • Get drop-downs in the Workbook for static and dynamic lists to select from. For example, Type Of Paper, Workflow Action, Org Unit, Lookup/Cascade Attributes, etc.
  • Easily differentiate each column in the Workbook for mandatory, user selected, Information fields due to the color-coding.

Feature highlights: 

  • Optimal use of APIs and parallel processing for improved performance, thus allowing multiple users to add multiple batches of files simultaneously. 
  • Eliminates the need of using a third party application such as Excel Add-in to upload entities in bulk.
  • Ability to select Attributes from ICI user interface (which is not possible when using Excel Add-in).
  • Ability to check the number of valid Templates for an Amendment when using Own Type of paper.
  • Access control by showing the Bulk Actions tile only to users with Manage privileges.
  • Provides error and status files for every batch processed. The status file indicates if the records passed or failed the validations. The error file indicates the specific validation errors while processing the batch.

You can enable the Bulk Actions tile through the Security Groups. 

To enable the Bulk Actions tile: 

  1. Click User Administration > Security Groups > Security Groups on the Home page. The Security Groups index page opens. 
7.12 BulkActions 1.png
 
  1. Click the View Record icon next to the Security Group you want to view. The Security Group Details page opens.
7.12 Edit Sec grp.png
 
  1. Click Edit. The Edit Security Groups page opens.
7.12 Edit Sec grp 2.png
 
  1. Navigate to the Privileges section in the Security Group and search for Bulk Action under the Entity Name column. 
 
Edit Security Group
  1. Select Bulk Action option under Manage or View column depending on whether you want to provide Manage or View privileges to the Bulk Action tile. The Bulk Actions tile will be displayed on the Home page. 

The Bulk Actions tile enables you to:

  • Update Existing Entities. For example making changes to Agreements that are in Executed state
  • Populate the Workbook.You can use the same Workbook to upload multiple Agreement records 
  • Add a new Batch
  • Process the Batch
  • View the Status and Error files  

Creating New Agreement using Bulk Actions

To create a new Agreement:

1. Click Bulk Actions tile on the Home page. The Bulk Action Management page opens.

2. Click the Create New tile. The Create page opens with 2 tabs: Details and Attributes

3. In the Details section, select Create Agreement from the Bulk Upload Action drop-down.

7.9 Bulk Actions - Create Agreement - User Provisioning.png
 
4. Select a Contract Type Name from the drop-down list. The respective Associations of the Contract Type are displayed. Mandatory Associations are auto-selected and can not be removed.
5. Select Association(s).
 
Bulk Actions Create New with Association - New 1
 
6. Click Next. All Attributes related to the Contract Type and the Associations will be loaded on the Attributes page. User can select the Attributes. The mandatory Attributes may already be displayed. 
 
Bulk Actions Create New with Association - New 2
 
7. Similarly, you can select the Associations.
8. Click Generate Workbook. The Workbook will contain the users selected Agreement, Associations and the selected Attributes.
 
RTENOTITLE
 
9. Download the Workbook. The downloaded Excel file will display:
  • The mandatory Attributes (such as Contract Value) are in red
  • The non-mandatory Attributes (such as Name) are in white with a light green background
  • The system Attributes are in white with a dark green background
  • The information Attrbiutes are in white with a blue background
Note: Do not edit the headers as well as system attributes. However, the mandatory Attribute values must be entered. 

 

RTENOTITLE
 
10. Enter the Parent Agreement Name and the Name; the child name properties are automatically displayed. The downloaded file will also contain an Information sheet which contains the information of the Actions (such as Create Agreement) selected by the user and the Sheet Names (Peer Association) with the defined configurable Linkage Type values for the association.
 
7.15 586492 23.png
 
Note: The Sheet Names have a 30-character limit. Currency code, Third Party Paper, Organization Unit, etc. are dynamic values fetched from the Contract Type.

RTENOTITLE

11. Upload the Workbook with all the sheets as a zip file.

12. Click Add Batch. The Add Batch window opens.

  1. Enter the Batch Name
  2. Select the Data File
  3. Select the Attached Zip File

RTENOTITLE

13. Click Add. The batch file is displayed on the Bulk Action Management Index page with a statusAdded to Queue. The status changes toCompleted when the batch is successfully uploaded.

RTENOTITLE

14. Click the arrow in the Action column of the batch to download the status file. The Download Status File window opens.

RTENOTITLE

15. The Status File displays the status of the files that are uploaded successfully, partially or failed to upload. The Status column displays the status of the files and the reason for partial success or failure is displayed in the Reasons column. For example, if an Association fails but the Agreement is successfully uploaded, then it will be a partial success.

RTENOTITLE

16. Click the Error File button on the Download Status File window to download the error processing file to understand the reason for failure.

RTENOTITLE

Note: Follow the same process to create new Masterdata.

Adding an Amendment using Bulk Actions

Enabling Attribute inheritance for amendments

615291-Enabling attrinute inheritance 7.15.png
 

1. Click View Record icon corresponding to the contract type you want open. For example, ICMAutomationBasicAgreement. The Contract Type Details page opens.

615291-Enabling attrinute inheritance 7.15-1.png

2. Click Edit. The Edit Contract Type page opens.

615291-Edit Contract Types-7.15.png

3. Click Next. The Attributes page opens.

4. Select the Attribute in the Selected Attributes pane. For example, Contract Value. The Edit Attributes section opens.

5. Toggle On  the Is Inherit On Amendments field.

Note: By default, the Is Inherit On Amendments property is On for attributes. Configurator should consider the behavior of the rest of the attribute properties along with Is Inherit On Amendments before setting it to Off.

615291-Is Inherit on Amendments.png

6. Click Save. The Attribute will be updated.

7. Click Next. The Association page opens.

8. Enter details in the Association, Display Preference and Team tabs.
9. Verify the details and click Update. The Contract Type will be updated.

1. Click Bulk Actions tile on the Home page. The Bulk Action Management page opens where you can update the existing entities by adding Amendments using the Update Existing tile. 

2. Click Update Existing on the Bulk Action Management page. The Update page opens. 

Update_Existing_Entities

3. Perform the following actions on this page: 

  • Bulk Upload Action: Select Add Amendments from the drop-down. This helps in adding an Amendment to an existing Agreement.
Note: You can add Amendments only to Agreements in Executed state. 
  • Saved Search: You must have a Saved Search created before you can update any entity. Select the Saved Search from the drop-down, that shows all the Saved Searches by the logged in user, as well as Global Saved Searches. 
  • Contract Type Name: Select the Contract Type name from the drop-down. The user can view only those Contract Types that are associated with the Saved Search, and to which the user has access to. 

4.Click Next.

 
7.9 Bulk Actions - Update Existing - User Provisioning

Selecting Attributes 

When adding an Amendment to an existing Agreement, select only the Attributes that you want to modify.

Note: Values for non-editable Attributes and system Attributes such as Agreement Code cannot be selected. The metadata for the remaining Attributes is copied as-is from the parent Agreement. 

This page displays only Attributes related to Contract Type you have selected. You can select only the editable Attributes. If you select a dependent Attribute, the primary Attribute also gets selected by default. The Attributes selected on this page will be visible in the Workbook you generate. For example, Effective Date and Expiry Date

To select any additional Attributes: 

  1. Select the Attributes from the Available Attributes list and move it to the Selected Attribute column. For example, Use Amendment Template. Click Yes when prompted to add parent Attribute. 
  2. Click Generate Workbook. This generates and downloads the Workbook with the system Attributes that are inherited as well the Attributes that you selected. 
Note: The file name of the downloaded Workbook is the same as the Contract Type you selected on the Details page. 
 
615291-GenerateWorkbook1.png
  1. Open the Workbook that was downloaded  on your local drive. This Workbook contains the information about the selected Attributes and Contract Type. 
The attributes which have inheritance enabled for amendments will have their values copied from the base agreement and are auto-filled in the workbook. For example, attribute Contract Value has its values copied from the base agreement ICM Automation Basic Agreement.
 
615291-View workbook on bulk actions1.png
 
 
Notes
  • The Is Inherit On Amendments attribute property is only available for Agreement contract types.
  • When the Is Inherit On Amendments is set to Off for an attribute, its value will not be inherited to its amendment.
  • The technical configuration settings for excluding base agreement attributes from its amendments will always take preference over the settings at agreement contract type and template level. For example, if the attribute Contract value has Is Inherit On Amendments set to On at contract type level, but set to be excluded in a config key, the value for Contract Type will not be inherited to its amendment.
  1. Click the Enable Editing button on the Excel Workbook to make changes as required.

Populating the Workbook 

The Workbook that was generated in the previous step contains the Attributes you have selected as few additional system Attributes. You should see the following Attributes in this Workbook: 

  • Parent Agreement Code: This is a system-generated field, the value of which should not be changed as it will result in an error. It contains the Agreement codes of the Agreements that are part of the Contract Type you selected. 
  • Effective and Expiry Dates: These are user-editable fields that are included in the workbook because we selected them when generating the Workbook in the example above. 
  • Use Amendment Template: This Attribute plays an important role in selection of the Template when creating the Amendment. The system will: 
    • Either use the specified Template or,
    • The last approved version of the Template in the parent Agreement or,
    • Auto-select a Template based on various combinations of this Attribute such as Type Of Paper, Template Name and File Path Attributes

User must select this Attribute on the Attributes page to achieve the desired result as mentioned below: 

  • If the Type Of Paper is Own and a valid Template name is specified in the Template Name column, then ICI attaches that valid Template to the Amendment. 
  • If the Type Of Paper is Own, the Use Amendment Template is set to True, and the Template Name column is blank, then ICI automatically selects the valid Template. If there is exactly one Template applicable for the combination of the Attribute metadata, the ICI automatically selects that Template to create an Amendment. If there are several valid Templates that are applicable, the ICI generates an error and provides a list of Templates to select from.
  • If the Type Of Paper is Own, the Use Amendment Template is set to False, and the Template Name column is left blank, ICI selects the last approved version of the parent Agreement to create that Amendment.
  • If the Type Of Paper is Third Party and user specifies the file name in the File Path column, the specified file is used to create that Amendment.
  • If the Type Of Paper is Third Party and File Path column is left blank, ICI uses the last approved version of the parent Agreement to add that Amendment.
  • Parent Agreement Status:This is a system-generated field, the value of which should not be changed as it will result in an error. It indicates the status of the Agreement to which you are adding the Amendment. When adding an Amendment, the parent Agreement status will always be Executed. 
  • Organization Unit: This is a system-generated field, the value of which should not be changed as it will result in an error. 
  • Type of Paper: This is mandatory and user-editable Attribute, the values of which may be Own or Third Party.
  • Template Name: This is a user-defined field. If the Type of Paper is Own ,the value in this field is considered when adding an Amendment.
  • File Path: This is a user-defined (editable) field. If the Type Of Paper is Third Party the value in this field is considered when adding an Amendment. Specify the complete name of Agreement document, including the file extension such as .pdf, .docx. The file name mentioned here must be part of the zip file you upload to ICI when adding a new batch.
  • Actions: This field is used to specify the workflow action. In this release, only Create action is supported.

Understanding the Information Sheet

  • ICI adds a default sheet named Information, where you can find general information about the Upload action you have selected as well as the mapping of Contract Type name with sheet names. 
  • Do not make any changes to this sheet.
  • When the records have been updated and the Workbook is populated, you must create a zip file that contains all the files mentioned in the Workbook, including the file names mentioned under File Path column, or the file names mentioned under Attributes with File data type. This zip file is required for performing the next step of Adding a new Batch
  • The zip file can contain all the file formats supported by ICI, and can be up to 100 MB in size. 

Adding a new Batch

You must create a batch to update existing Entities in ICI, such as new set of Amendments. Creating a new batch enables the system to upload all the changes you made to the workbook and process them. The number of records in the batch is indicated in the Batch Size column.

You can create a batch using the following steps: 

  1. Click the Add Batch RTENOTITLE  icon on the Bulk Action Management page. The Add Batch window opens from where you can upload the populated Workbook to ICI.
RTENOTITLE
  1. Enter the Batch Name. For example, AutomationAgreement.
  2. Click Choose File next to the Data File field to select the Workbook to upload. You should upload the Workbook that you populated in the previous steps. 
  3. Click Choose File next to the Attached Zip File field to select the zip file that contains all the files you have mentioned in the Workbook, either as a File Path or as  File Type Attribute.
  4. Click the Add button. The Workbook will be uploaded to ICI with a status of Added to Queue. The batch is added to the queue for automatic validation. 

</div>

Processing the Batch 

The Batch that you added in the Adding a Batch section will be processed by ICI. Multiple users can create multiple batches at the same time. These batches would be queued and ICI would pick them up for processing from the queue. The status of the batch can be as follows: 

  • Added to Queue: This is the status of the Batch when you upload the Workbook using the Add Batch button on the Bulk Action Management page. ICI validates the accuracy of the records in the batch. 
  • In Process: Indicates that the batch is being processed after the user has uploaded the batch. 
  • Completed: The status of the batch changes automatically to Completed after the batch is processed. 

While processing the Batch, every record is validated for:

  • Correct data type for all records being uploaded. 
  • Any Template that may have been selected is correctly added.
  • All files specified in File Path column or File Type Attribute of the workbook are physically present in the uploaded zip file. 
  • In case of Add Amendments Upload action, Agreements of the selected Contract Types are in Executed state.
  • Lookup and Cascade Attributes validation:
    • Lookup Attribute: Based on the Masterdata, specific values will be displayed for selection. For such Attributes, ICI checks if the value you have specified is present is the Masterdata or not.
    • Cascade Attribute: Based on the value selected in the Lookup Attribute, specific values will be displayed for selection. For such Attributes, ICI checks if the value you have specified is valid for the combination of lookup value and the Masterdata associated with it.

Bulk Action Management 

Clicking the Bulk Actions tile navigates you to the Bulk Action Management page.

The following tasks can be performed here:

  • Adding a new batch 
  • Viewing the status of a batch 
  • Updating Existing Entities 
To view the status of the batch, click the   icon on Bulk Action Management page. 
 
RTENOTITLE

The following columns are displayed here:

  • Status: displays the following states of the batches that are processed.
    • Added to Queue: indicates that the user added a new batch for processing.
    • In Process: indicates that the batch is being processed after the user has uploaded the batch. 
    • Completed: indicates that processing of the batch is complete, even though errors might be encountered when validating the records. 

The Download Status Files icon appears in the Actions column after the status of the batch changes to Completed. Any errors during the processing of the batch are displayed in the Failure column on the Bulk Action Management page.

  • Success: displays the number of records that passed the validation process.
  • Failure: displays the number of records that failed the validation process.
  • Start Time: displays the Date and Time when the batch processing started.
  • End Time: displays the Date and Time when the batch processing concluded.
  • Execution Time: displays the Time taken to process the batch and change the status of the Batch to Completed.
  • Created By: displays the name of the user who created the batch.
Note: By default, users can view only the batches they have added to queue. The Administrator can view the batches for all users.

Viewing the Status and Error Files 

After a batch is processed, a Download Status Files icon is displayed in the Actions column.

To view the files: 

  1. Click the Download Status File icon. The Download Status Files window opens
  2. Click the Status File or Error File to download the applicable file of the batch. 
RTENOTITLE
  • The Status File shows the status of the records that were processed in a batch along with any failures.
  • The number of failed records in the file will correspond to the number in the Failure column on the Bulk Action Management page.
  • The Warnings and Errors columns in the Error File indicates the specific issue. If the validation of a record fails for multiple reasons, then all such reasons are mentioned against that record.
  • If you want to process the failed records, then you must create a new batch and upload a Workbook that contains corrected values of the failed record. You are not required to start the process from the beginning (select Upload action, select Attributes, and so on.) You can reuse the Workbook that was generated earlier. All records that have been successfully created in ICI can be viewed from the UI.

 

 

Updating the Existing Entities

1. Select the Update Existing tile on the Bulk Action Management window. The Update page opens with the Details tab active.

2. Click the Bulk Upload Action drop-down. The following Bulk Upload Actions are available:

  • Add Amendment
  • Update Agreement
  • Update Amendment
  • Update Executed Agreement
  • Update Executed Amendment
  • Add Association to Agreement
  • Add Association to Amendment
  • Initiate Termination
RTENOTITLE
 
3. Select Update Action from the drop-down list. For example, Update Agreement.

4. Select Saved Search. All saved searches that the user has access to get populated in the drop-down.

5. Select Contract Type Name. This list will be populated based on the selected Saved Search.

6. Select Association(s) that you want to update for this Agreement.

7. Click Next. The Attributes tab is active. You can now select the Attributes for the selected Agreement and the Associations.

RTENOTITLE

8. Click Generate Workbook. The Workbook will contain the Agreement, Associations and the selected Attributes. You can make changes, upload the files to ICI and continue with the workflow.

Note: Follow the same process to update other entities.

 

Initiating the bulk termination for agreements

To initiate bulk termination:
1. Click Bulk Actions on the Home page. The dropdown opens with the options for bulk actions.
2. Click Update Existing. The Update page opens.

7.15 514625 1.png
 
3. Select Initiate Termination in Bulk Upload Action field.
4. Select a Saved Search. For example, Executed_Agreements. Users need to create a saved search with executed agreements for which termination agreements can be created.
5. Select Contract Type Name. For example, ICMMasterServicesAgreement. The Contract Type Name field displays all the contract types from the selected saved search.

7.15 514625 2.png

The Alert window with the error message is displayed if the user selects the contract type which does not have the required configuration and attributes configured for the termination process.
 
6. Select the Termination Contract Type Name. For example, ICMTerminateMasterServicesAgreement. The Termination Contract Type Name field displays all the contract types that can be used as termination agreement for the selected contract type name.
7. Select the Association if you want to update for the selected Termination Contract Type.

7.15 514625 3.png
 
8. Click Next. The Attributes tab opens.
9. Select the desired attributes for the selected agreement and the associations.

Note: The attributes related to termination process (Termination Date, Termination Parent Id, Is Termination) are pre-selected and cannot be removed.

7.15 514625 4.png

 

10. Click Generate Workbook. The workbook is generated with the executed agreements from the Saved Search, Associations and the selected Attributes. For example, ICMTerminateMasterServicesAgreement_20201210143128
The attributes which have enabled the inheritance, will have their values pre-populated from the parent agreement.
 
7.15 514625 5.1.png7.15 514625 5.2.png

 

11. Edit and upload the workbook files to ICI following the standard ICI bulk update action workflow by adding and processing a batch.


Once the batch processing for the bulk action is successfully complete, the termination agreement is created in a Draft status and associated with the parent agreement. Users can then proceed with the standard agreement workflow and execute the termination agreement. The parent agreement then, will be terminated according to its termination date through the scheduled termination processes.

 

 

Related TopicsAgreement Management | Agreements | Add Amendment to an Agreement