nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

D2 and TBO

prasan_13

Has anybody figured out a way to avoid calling particular code within a TBO if the call is coming from D2.Is there some condition we can check.

We basically are trying to figure out a way where we have a TBO , We don't want the TBO functionality to be called when the call comes from D2 but it should be executed when the call comes from a different client say DA or Records?

Thanks

Find more posts tagged with

Comments

Antal Bos

Hi,

The most simple thing you can do is creating a subtype of that dm_type object where you created the TBO for and use a preset in the object_name.

So your custom dm_type (e.g. my_document) will have a d2 variant (e.g. my_d2_document)

Best regards,

Antal

prasan_13

I don't think it's feasible for us to change the object model for this. Is there any way we can check by code within the TBO if the call is originating from D2 and then ignore the executing functionality if it did?

albertocb

You can add an attribute to the type that indicates where the document was created (D2 or other app). Use a default value template to populate by default the attribute in the D2.

prasan_13

Thanks for the options. but we were able to check the stack trace in the TBO and then ignore the loop when the call came from D2

albertocb

Just saw you commented (D2 Interoperability Guide):

// Determine if this object save originates from a D2 method

boolean calledByD2 = false;

StackTraceElement[] stack = new Exception().getStackTrace();

for (StackTraceElement s : stack) {

if (s.getClassName().contains(".d2.") || s.getClassName().contains(".d2fs.")) {

calledByD2 = true;

break;

}