IBM TAS Connector for Envizi

Navigate to Tools > Administration > Object Migration and select New Import Package to begin the import process. Select the APIConnector OM Package in the TAS instance. In the pop-up window, select Validate to validate that the package can be imported properly and then Import to start the import process.

For more information, see IBM® TRIRIGA documentation.

The users are now be able to interact with the proper TAS Modules.

For users to pull from these URLs, the minimum requirements are:

1. Navigate to Tools -> Builder Tools -> Data Modeler and using the Object Browser navigate to Location->triBuilding.
2. Revise the BO and add four fields:
   • cstEnviziParentOneTX
   • cstEnviziParentTwoTX
   • cstEnviziParentThreeTX
   • cstEnviziGroupNamePathTX
   

Name and Label should be the following:

After entering these values, click Publish to publish the BO.

1. Under Tools -> Builder Tools -> Form Builder, click on the Location module on the left side of the screen and then click triBuilding.
2. Revise the triBuilding form by clicking Revise in the top right corner of the pop-up
3. In the Navigation pane on the left side of the screen, click on triBuilding and then Add Tab. Enter cstEnvizi as the Name and Envizi as the Label. Click Apply
4. Select this new tab and click Add Section.
5. Enter cstEnviziDetails as the Name and Envizi Details as the Label. Click Apply.
6. Click on the newly created Section and select Add Field. Select each of the four created business objects from the previous step as fields under Envizi Details.
7. Select cstEnviziGroupNamePathTX and modify Start Row to 3 and Col Span to 2 on the properties window. Mark this field as ReadOnly and click Apply. The form should look like this:
8. Click triBuilding on the left panel and then click on Sort Tab. Move the cstEnvizi tab to the second position and click Apply.
   
9. Publish the form.

1. Navigate to Import Migration and import package EnviziConfig.zip by clicking New Import Package, select the zip file, and then click OK.
2. A new window is displayed. If it is not displayed, just select the package from the list.
3. On this package, click Validate and wait for the validation to complete. If no errors are displayed, import the package.

1. Go to Tools -> Administration -> Security Manager. This application sets who can and cannot access this newly created tab.
2. Click the newly created name of the group, and navigate to the Access tab.
3. On this tab select Location -> triBuilding -> cstEnvizi.
4. Choose the access level for the group and click Save.
   

1. Go to Tools -> Builder Tools -> Workflow Builder. Select Location -> triBuilding.
2. Within the Location object, search for the existing Workflow triBuilding - Synchronous - Permanent Save Validation.
3. Revise this workflow and after Call Module Level Validation, add a new Workflow call to triBuilding - Update Envizi fields with defined options like displayed below:
   

It will be defined as the image below:

Click the Start task at the top and publish the workflow.

1. Go to My Reports and navigate to System Reports. Add those four new fields to the existing query triAPICBuilding - OSLC -- Outbound by clicking the Columns tab and adding the four fields like below:
   
2. Save the report.
3. Open Tools -> System Setup -> Integration -> OSLC Resource manager and search for triAPICOutboundBuildingRS. On this resource, add the four new fields either individually or by using the Import all Fields option.
   

1. Go to Tools->Builder Tools-> Navigation Builder and find TAS Global Menu (or the menu associated to the user that will need access to the app). Select and click Edit.
   
2. On navigation Items section, expand Landing Page –Tools -> Menu Group –>System Setup. Select Menu group –>Integration and expand Navigations Item Library.
   
3. Search for Envizi, select the item, and then click Add to Collection.
   
4. Click Save.
5. Log out and Log in again to the system.

This tool allows you to make changes on this new Envizi group name fields. But the existing records must be taken into consideration as well. If you want those records to be populated, there is a patch helper workflow that can handle that.

The first thing that must be defined is which fields are used to populate groups 1, 2, and 3 to be used on Envizi. To access the Envizi tool, go to Tools -> System Setup -> Integration -> Envizi Integration. When you open the page, the fields are displayed as Group1/Group2/Group3. By default, the values are World Region/Country/City. The Envizi Hierarchy Path field shows how the Envizi group names are configured, according to the selected option.

Enable Envizi check box is also available. The Envizi tab is displayed only when this check box is marked. One more item that must be configured is the Number of levels to be used on the Envizi configuration. Envizi hierarchy path matches this selection.

Also, notice that there is a section named Active/Retire with missing data and Draft/Revision with Missing Data. This section lists the buildings that don’t have data defined for Envizi group 3, so it means that no Envizi group is populated on those buildings.

You can filter to change only the desired records by changing query cst -triBuilding -Query -Get All Buildings for envizi. The list of buildings displayed on this query is the list of buildings that the patch helper modifies. To use the tool, just select the desired Envizi group names and click Save. Once the Save action is triggered, all buildings are populated with the desired options. This process might take a few minutes depending on how many buildings you have on your system. After that Envizi groups and path is updated according to the selections made on Envizi Integration page.