"Form action definition is out of date" Simple fix

Recently I decided to modify the SSM - Incident Management workflow in my SBM 11.2 instance. I made the changes I wanted in Composer but when I tried to validate I saw all kinds of issues!

Validation Errors

The error was in several form actions and stated “Form action definition is out of date and needs to be upgraded”. I was unable to deploy the process app! I wanted to fix it but how do you upgrade the form action definition? Luckily it was an easy fix.

Double click the error description and open the form action to edit. Next to the form actions that have issues you will see a refresh icon.

Refresh action

Simply click the refresh icon and click "OK" to close the dialog box. Do this for all the form action errors listed in the Validation Results and you should be able to deploy your process app again.

The errors are due to several new changes in form actions in the latest release 11.2. These changes include a change from ‘rule evaluates to true’ to now ‘rule evaluates to true/false’ as well as a change that consolidates form actions which operated on field and on controls into a single one which operates for both.

Continue reading
106 Hits
0 Comments
Featured

How to test GSOAP webservice call

We have all had that issue with the Repository or the Orchestration Engine being unable to get to the gsoap web service URL.  And, this is with all SBM components installed on the same server.  Why can't it get to itself?  Or in the case orchestrations, maybe we cannot figure out why the OE is unable to reach a third party web service.

Continue reading
224 Hits
0 Comments

How to get json listing from SBM JSON Report in SBM 11.1 and above

Background:

 

SBM Aurora (11.1) had introduced authentication with both javascript and json.  The old method of using the embedded report reference link (tmtrack.dll?ReportPage&template=reports%2Fjsonlist.htm&ReportRef=TRM_DEPLOYMENT_PATHS.Deployment.Paths.By.ReleaseType.and.Applications&HasRuntimeParams=1&") does not work.

 

Solution:

 

The current documentation (json_api_guide.pdf) example is not clear on the usage.  Use the new json api

 

tmtrack.dll?JSONPage=&command=jsonapi&JSON_Func=GetitemsByListingReport&JSON_p1=Deployment%20Paths&JSON_P2=Deployment.Paths.By.ReleaseType.and.Applications&HasRuntimeParams=1&F_TS_RLM_APPLICATIONS=30&F_TS_RELEASE_TYPE=1";

 

JSON_P1 refers to the display name of the database table

JSON_P2 refers to the Reference Name of the Report (Not Reference Link)

Parameters such as F_TS_RLM_APPLICATIONS are located behind

Continue reading
335 Hits
1 Comment

Create a Draft State in SBM - easier than before

A couple of years ago, a colleague of mine wrote a blog about implementing a Draft state in SBM.  This has been a common request and is quite simple to configure.  His blog here outlines how to implement a bonus capability with a specific button to "Save as Draft" instead of the user clicking a check box and then clicking ok.  From a usability standpoint, it is easier on users and flows better.

Since the time of that entry (2015) we have made significant advancements in SBM and now you can implement the functionality described in that article with a form action and not all of that complex JavaScript.  

Continue reading
367 Hits
0 Comments

Line Item Creation - Insert Rows in Grid/Listing

The information contained in this blog post provides a way to implement a solution for line items on invoices, expense report entries, time entries or other ideas you may have that would require a user to enter a list of items with multiple fields per entry.

Continue reading
515 Hits
9 Comments

Recent Tweets