How do you use the saveRecord() with state transitions in CBA?


The IBM TRIRIGA Connector for Business Applications (CBA) has the saveRecord() method. If saveRecord() runs without an action parameter, it triggers not-audited field validation (read-only, formulas, etc.). Is it fine to use this method without an action name?

For example, saveRecord could call a state transition by its name in a parameter. But a record could be in any state, so this state transition could be not-applicable to the current state. What if a record receives the wrong transition? (I guess InvalidActionNameException.) Should this situation be handled by process design? Or by state validations in the code which is difficult to maintain? Or another way?

[Admin: To see other related posts, use the CBA tag or Connector tag.]

Continue reading

Advertisements

How do you migrate record data quickly between environments?


So I just learned that I can’t use the Object Migration tool to migrate record data between two TRIRIGA environments. For example, I have two environments on different servers on the same application and platform version. If I try to use OM to migrate the Record Data only, for instance, the Building Equipment records, not all of the associated records will get migrated and certain smart sections do not get properly migrated either.

What are some other options that I could use to quickly migrate this data? I was thinking the Data Integrator (DI) method, but that would be tedious because I have over 100,000 records.

Ideally, DI should be used for the initial load. If the data is available somewhere else, you can look into Integration Object or DataConnect. You can populate staging tables and then run the integration. In your workflow, you can have logic to create any dependent records (such as organizations or contacts) based on the staging table data.

[Admin: To see other related posts, use the Integration tag or DataConnect tag.]

Continue reading

How do you configure TRIRIGA for Tivoli Directory Integrator (TDI)?


You can configure TRIRIGA to use Tivoli Directory Integrator as its ETL runtime engine to run ETLJobItems from within TRIRIGA.

Before you begin

Install Tivoli Directory Integrator, if not already installed, on all the TRIRIGA systems that could run a TDI ETL Job Item.  During the TDI install:

  • Make note of the installation directory you enter on the Destination panel. You will enter this value later in TRIRIGAWEB.properties.
  • Select either installation type. TRIRIGA requires only the TDI Server component.
  • When prompted for the location of the Solution Directory, you can select any option. TRIRIGA specifies its own solution directory at runtime.  However selecting the option “Use Install Directory” may simplify troubleshooting.
  • Make note of the value you enter in the Server Port field on the Server Port Values Panel. You will enter this value later in TRIRIGAWEB.properties.
  • Clear the “Start the Configuration Editor” check box on the Install Complete panel.
  • Note: This step is very important for TDI/TRIRIGA integration to work. After you have installed Tivoli Directory Integrator, update it with the recommended fix packs (per TRIRIGA support matrix). TDI must be at least at FP04 (7.1.1.4) or it  will not automatically start the TririgiaETLDispatch.xml assembly line which will result in ETL job items failing to run successfully.

Procedure

  1. Edit TRIRIGAWEB.properties file to enable TRIRIGA to manage TDI server.  Set the following properties…
  2. Install a JDBC driver library so that Tivoli Directory Integrator can use it to access TRIRIGA database…
  3. Edit TDI global.properties file to allow TRIRIGA to check and stop the TDI server from localhost without requiring authentication and authorization certificates. Set the api.remote.ssl.on property to false to tell TDI to trust requests from localhost…
  4. Start Tivoli Directory Integrator Agent from TRIRIGA Admin Console and verify that it starts successfully…

[Admin: This post is related to the 08.03.16 post about installing, upgrading, or uninstalling TRIRIGA TDI, and the 05.01.16 post about documentation on developing TDI with TRIRIGA. To see other related posts, use the TDI tag.]

Continue reading

Is there a way to get the proper date value for CBA?


Our workflow sends an outbound message by user action. For the Connector for Business Applications (CBA), the Connector user guide says:

For date values, the outbound query results include the raw values that are stored in the database and the formatted display values that are shown to the user. The displayValue node is added to the query results. The following example shows the default XML structure…

But for us, the outbound message has a different format… The <value> is presented in the same way as <displayValue> which is not acceptable because users may have a different date format. Is there a way to get the proper date value in <value> or use a single <displayValue> format for all users?

Continue reading

How can you leverage IBM Watson Analytics for your TRIRIGA data?


Watson Analytics is an intuitive, cloud-based analytics tool that will help TRIRIGA users explore their data for insights and display findings as dashboards and infographics for easy sharing. All without having to become a data scientist.

Watson Analytics guides data discovery and predictive analytics by using automatic visualizations and enables dashboard creation so that you can get insights and make informed decisions. Pairing Watson Analytics with data from TRIRIGA enables you to explore your integrated workplace management processes and obtain new insights on your day to day operations. The IBM Watson Analytics service will allow you to discover patterns and meanings in your data.

The TRIRIGA Connector for Watson Analytics gives you the ability to export your TRIRIGA data into Watson Analytics. With Watson Analytics, you can tune data, discover insights to help solve your business problems, and display your findings…

[Admin: To see other related posts, use the Watson tag or Analytics tag.]

Continue reading