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

Why is the lease record stuck in “Processing” during activation?


We are running TRIRIGA 10.5.2 and 3.5.2.2. Some of our lease records are getting stuck in “Processing” status after we try to activate the record. Since it is processing, we have no buttons at the top to Revise, Save, etc. This only happens sometimes, and only to lease records that have payment schedules. From the looks of it, all the payment line items do get created. A couple questions:

  • (1) Is there a fix to this to keep it from happening again?
  • (2) Can these records that are stuck in processing be pushed to active or do they have to be re-entered?

I was actually able to apply a workflow fix provided by IBM so that this will not happen going forward. So far, it has been working as planned…

With regards to getting the leases “unstuck”, I created an editable query, imported the State Transition Actions (on the Advanced tab in the query form), and ran the report to select and process the “stuck” leases. This worked with no issues and I did not have to delete or retire the leases. They were functioning properly after getting them out of the “Processing” state.

[Admin: This post is related to the 01.12.16 post about records getting stuck. To see other related posts, use the Performance tag or Workflow tag.]

Continue reading

Can you retire a job plan to get rid of unneeded draft work tasks?


When the Operations team was changing a job plan, the wrong date was entered, and it created over 1,800 work tasks. They have since tried to retire them and they changed to Draft status. To get rid of these, can the job plan itself be retired?

[Admin: To see other related posts, use the Job Plan tag.]

Continue reading

IV97411: Adjusting task status on Gantt not working uniformly


Adjusting the task status on a Gantt chart with Ctrl/Cmd+click is not working uniformly across client operating systems.

We needed to disable the Ctrl+left/right-click and Shift+left/right-click, which are not working consistently across browsers and Mac, and reintroduce the right-click > “Set Percentage Complete” to the right-click menu. We also needed to update the “Percent Complete” message to be shorter, and update the message minimum width to be wider.

Moving forward, we removed the ability to set the percentage complete by using Ctrl+click, which does not work correctly on all browsers on all operating systems, replacing it with the ability to “Set Percentage Complete” by using the right-click context menu when right-clicking a Gantt task.

[Admin: To see other related posts, use the Gantt tag.]

Continue reading

Is there a way to set editable fields to be read-only conditionally?


I’ve noticed that if the record is read-only in its current state, we can still edit this record via the editable query. Is it possible to set editable fields, or the whole record, to read-only conditionally? For example, according to status?

Unfortunately, the platform does not handle this requirement. I would recommend adding a request for enhancement (RFE) for consideration in a future release.

[Admin: To see other related posts, use the Editable tag.]

Continue reading

IV95382: Agent performance monitors not working properly


In the Admin Console, Performance Monitor, when monitoring a single value, it returns bad results. Returns wrong agent’s status. Returns “false” for an agent status even if the agent is running. Returns “0” for the number of agents running even if multiple agents are running.

We needed to update the calls to various platform status APIs. Moving forward, we updated the Admin Console, Performance Monitor, Single Value to correctly obtain the status of the active agents. This means the AGENTS_RUNNING_COUNT, OBJECT_PUBLISH_AGENT_RUNNING, SCHEDULER_AGENT_RUNNING, and all other agent-related monitors will now correctly report the agent status and count. We also removed the calls to KEYWORD_PARSER_AGENT_RUNNING and WAREHOUSE_AGENT_RUNNING as these no longer exist.

[Admin: This post is related to the 04.08.15 post about performance monitoring tools, and the 02.10.17 post about performance best practices.]

Continue reading

Are there any known limitations when creating a pie chart?


Are there any known limitations with pie charts in the TRIRIGA Report Manager?

We created a chart, but the available data meant it should show 100% for a single status value. However, the report just says “No data to display”. Expanding the filter to bring in more records meant that we had multiple status values to display and the chart displayed correctly. Is there a limitation on a pie chart so that if the result set is 100% in one grouping, it doesn’t display anything?

This is a known issue covered in APAR IV95291. You can subscribe to the APAR for updates on the fix.

Continue reading