Changing related workspaces created by Salesforce using Webreports

Hi,

I have an business app integration with Salesforce that creates different types of Business workspaces and some of them have a child-parent relationships.

From my understanding, these relationship are stored in the otsapwksp_bo_child_relations/otsapwksp_bo_parent_relations tables and I can see them in my database.

Based on some testing that I did, if I were to manually add(Including webreports) a parent/child relationship to the same types of workspaces they would actually be stored in the otsap_wksp_relations table. In the same line of idea, it seems like I can't manually(Including webreports) remove a relationship between 2 workspaces created by Salesforce that is stored in the otsapwksp_bo_child_relations/otsapwksp_bo_parent_relations tables.

Is there a way to manually add/remove a relationship between 2 workspaces that have been created by the Salesforce integration, or is it only possible through Salesforce.

Thanks!

Find more posts tagged with

Connected Workspaces

Note:

If there are Accepted Answers, those will be shown by default. You can switch to 'All Replies' by selecting the tab below.

Accepted answers

All comments

DarrenHodder

Hi Samuel,

If the NODEACTION sub-tag doesn't explicitly work on the parent child relationship, this would be a good candidate for a custom WebReport sub-tag drop-in. These are fairly quick and easy to develop specific functions like this.

Cheers,

Darren.

DarrenHodder

Hi Samuel,

I found an article Greg Petti wrote on this very topic of sub-tag dropins.

https://www.ravenblackts.com/blog/deep-dive-how-to-create-custom-sub-tags-for-webreports-and-activeview

appuq

I believe when a Leading application in your case Salesforce Force, creates a BOREFERENCE(Relation to be simple) then the Removal is accomplished by using an API that informs the Leading application

[LL_REPTAG_'314007' WKSPACTION:BOREF:REMOVE:"myexternalmaximosystem":"Locations":"BEDFORD:BPM3100" /]

In the above code, I found 314007 a Assets Workspace Linked to a Locations Workspace with the key BEDFORD: BPM3100. Related workspaces are typically something a user would find in their application. For example, in our product, https://www.qellus.com/qellus-extended-ecm-for-maximo we populate Assets(similar to Equipment in SAP) tied to a Location(similar to Functional Location). If one goes to the Asset Record, they will see on that Screen that it is part of the location BPM3100 of Bedford. That is what it is supposed to convey. There's also a curved ball to this when the Asset Workspace is created, and one specifies the Related BO; one is only sending KEY information. The actual linkage only happens if the related object happens, which is why, when you look at this table

The Related_ID_BO is shown and not the Dataid, like in the first column, as there is no certainty whether the Related_ID_BO has been created yet…In the GUI, you won't fulfill the linkage when the missing item gets created; the link will work.In the [OTSAP_WKSP_RELATIONS], it is easier as it doesn't actually show parent/child, and it is made up of existing objects, which is why they have actual dataids rather than the keys.I believe OT WR has a tag that allows you to work with BO Types(actual leading application connected and not its lesser functional cousin called "connected workspaces" )