Big news! The community will be moving to a new platform April 21. Read more.
Big news! The community will be moving to a new platform April 21. Read more.

SBM Relations - Part 2

SBM Relations - Part 2

 

Relating Records in SBM - Part 2

 

SBM Blueprint built using version 11.  Download Here ->  RelationsPart2.zip.

 

In the previous post, well previous…previous post, I introduced the ability to selected related records via the Relational Grid.  Or you could go the old fashioned route and use the relational fields themselves.  Either way is fine, the Relational Grid gives your users a better experience.

 

The example we will cover this time picks up once I select those related items, how do I go and update the downstream record’s relational field so that regardless of which record I am looking at, I can see the relations.

 

 

The short answer is to create an orchestration that sets the relational fields.  Then pretty up the presentation using Relational Grids.

 

The included blueprint contains two applications.  Primary Relationship Management and Children.  The Primary Relationship Management contains the parent records and the Children the children with the notion of a one (Primary) to many (children) relationship.  In the Primary workflow, there are two transitions.

 

1.      Create Child – This uses a post transition to create a child record into the Children workflow and establishes the relationship through the post transition properties and setting the relational fields when the child is created.

 

2.      Adopt Child – This transition allows the user to select one or more children, then when the user clicks OK, an orchestration is run to set the relational fields in both the parent and child records.  All of the forms, and orchestration steps are documented in the blueprint for your reference.

 

Then for fun, I decided to add orchestration on the Children workflow for them to select parents.  There are two transitions/orchestrations.

 

1.      Pick My Parent – Uses an asynchronous orchestration to update the parent record with the new child.

 

2.      SyncPickMyParent - Uses a synchronous orchestration to update the parent record with the new child.

 

To enhance the visibility you will notice that I have used Relational Grids.  The columns for a Relational Grid are defined with a Composer report.  This gives you a lot of flexibility in what you want to display about the records you are selecting or have selected.  In my opinion they are much more pleasing to the eye than the relational fields themselves.

 

Also notice that with the Relational Grids you can allow for searching by using the “Other Controls” on the palette.  I chose to have the user click a button to update the search results, you could as easily have the results auto refresh when the other control value changes.  These settings will be in the Results properties of the Relational Grid.

 

Included below are a couple of screenshots.  You can play around with the default and create more “Grid Styles” if you want to alter the coloring as I have with the purple you see below.

 

Selection of the available children:

State form with selected children:

 

Embedded Parent Record in child:
This is configured by setting the URL for the parent record in a field and then rendering that field in a webpage widget on the form.

 

 

Labels (1)

DISCLAIMER:

Some content on Community Tips & Information pages is not officially supported by Micro Focus. Please refer to our Terms of Use for more detail.
Comments
Hey Erika, Thanks for the wonderful blog post! This gives me some really amazing ideas for apps that I'm working on. However, I got an error when trying to open the example .msd file. The error text is copied below. Any idea what is going wrong?
Failed to import process app because of the following issues: The Application Definition entry is not valid: The element 'Application' in namespace 'http://www.serena.com/vail/definition' has invalid child element 'Locale' in namespace 'http://www.serena.com/vail/definition'. List of possible elements expected: 'ProcessModel, Dependency, BusinessSolution' in namespace 'http://www.serena.com/vail/definition'. Error importing Transition Form 'Transition Form': Value cannot be null. Parameter name: value Error importing State Form 'State Form': Value cannot be null. Parameter name: value The Endpoints entry is not valid: The element 'Endpoint' in namespace 'http://www.serena.com/vail/definition' has invalid child element 'AuthenticationTypeHint' in namespace 'http://www.serena.com/vail/definition'. List of possible elements expected: 'ServiceLocation' in namespace 'http://www.serena.com/vail/definition'. Error importing Transition Form 'Transition Form': Value cannot be null. Parameter name: value Error importing State Form 'State Form': Value cannot be null. Parameter name: value The Endpoints entry is not valid: The element 'Endpoint' in namespace 'http://www.serena.com/vail/definition' has invalid child element 'AuthenticationTypeHint' in namespace 'http://www.serena.com/vail/definition'. List of possible elements expected: 'ServiceLocation' in namespace 'http://www.serena.com/vail/definition'. Unable to resolve mapping: ForEachAdoptedChildRecord\item\internalValue
Hi Adam, What version of SBM are you using? I used SBM 11 to build out the example. Erika
I'm using SBM Composer Version 10.1.4.1 Build 016. Does this mean I will be unable to open your example?
Yes Adam, I am sorry about that. Do you have an upgrade in your near future? There are some great things in 10.1.5 and beyond! Erika
Well that's a shame. No upgrades in the near future that I'm aware of. I'm at the mercy of the company I work for, so we'll get an upgrade when they decide it's time. Thanks for the response!
Erica, that describes exactly what we need. We are @ 10.1.5 so I cant open the blue print. Do you have a description how to build a list with check boxes to select and the Adopt Child Orchestration? Jo
Erika - I managed to open the blueprind - clear so far - wel documented - like that ;). How would you set a respective Link Type - like "Two way no triggers"? Jo
 
 
Top Contributors
Version history
Revision #:
2 of 2
Last update:
‎2020-01-30 18:19
Updated by:
 
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.