SMAX-OO Integration - Execution Name in OO Central

[Alex Mata]

Syptom:

When SMAX calls to OO for OO Flow execution, the task created on OO, it's like: "SAW initiated flow execution: OPB task: 10cf86a5-db11-49ca-97d9-a52897210f6e". This mask is compliated for OO Administrators or users to know the OO invoked from SM

Requirement:

The task created must be called as workflow name invoked in order to easily tracking oo execution flows thought the OO Central.

See attachment (yellow highlighted)

CaptureOOExecutionName.JPG

[Tonya SMAX]

Thank you for sharing your idea! It’s open for comments and kudos, and we’re looking forward to input from the community. Once there is enough community traction, it will be further reviewed by the product team

[cheikh]

Hi,

As described above it is a little tricky to determine the executed flow, also for reporting proposes it’s necessary to get the flow real name.

[Tonya SMAX]

Thanks for all the votes and comments. We are looking into this as a future product enhancement. Check the notifications box to be emailed if the status changes.

[KolyaTLK]

Hello Alex

I wanted to ask for the same thing and then i see your post.Yeah it's really annoying for OO administrators 

It would be a nice to be able to customize the OO execution name in the SMA OPB. For example we would like to see the SMA offering name in the OO execution name

Also please do something for the mapping of OO Output Field result in SMA taskplans. If the flow failed we are forced to put the success response in order to be able to map the OO ouput Field in the SMA offering

Thanks 

Regards

[Tonya SMAX]

Thanks for all the votes and comments. We are looking into this as a future product enhancement. Check the notifications box to be emailed if the status changes.

[Tonya SMAX]

Great news, this idea has been accepted on our product roadmap, timing TBD. Check back for updates. (This is not a formal commitment, and subject to change)