Best Of
Re: Can I access certain metadata in Business Workflows?
Hi @Kamil_A, when the business workflow starts an advanced workflow, several variables are passed to it.
When the trigger is a file event (e.g.: file upload), these are the variables:
- documentName – name of the file
- wfd_trigger_file_id – id of the file version
- wfd_trigger_file_category_type – CMS (Content Metadata Service) file category of the uploaded file
- wfd_trigger_workspace_root_folder_id – id of the workspace instance where the file is uploaded to
- wfd_original_trigger_file_id – id of the file version, without any transformations
When the trigger is a manual action (e.g., from contextual menu), these are the variables:
- wfd_trigger_file_id_collection – ids of the selected file versions
- wfd_original_trigger_file_id_collection – ids of the selected file versions, without any transformations
User information is currently not supported.
Something you could investigate is passing information from the Core Content Management context (e.g., workspace attribute values) to the advanced workflow using data objects.
gvicari
Re: Override feature not working
in which case I would really recommend you do the formal OT Dev course and see if anyone in your firm can support / mentor you with the more advanced functionality as this will provide you with a good base to read / follow the more complex code so that you can reuse.
Documentation for Core Communications (CA) Export Package Structure and Field Definitions
I am currently developing a migration tool to convert PowerDocs templates from OpenText Content Manager to OpenText Core Communications (Communications CA).
As part of this effort, I have been reverse engineering Core Communications export packages to understand how templates and components are represented in their source files. The goal is to accurately generate equivalent structures during the conversion process.
While working with the export packages, I found that interpreting the JSON files is manageable to some extent. However, understanding the .bin files located in thecontent folder has proven to be significantly more challenging. In many cases, the associated JSON field names do not clearly indicate what the corresponding binary data represents or how it should be constructed.
This makes it difficult to reliably map and generate the correct fields during migration.
Is there any official or internal documentation available that explains the structure of Core Communications export packages, including detailed descriptions of fields and their purposes across all component source files (especially the .bin content)? Any guidance or references would be greatly appreciated.
ErikHo
Re: Override feature not working
Hey appuq,
You have no idea how much this really helps!😂
I can easily forward my learning journey with this, thank you!
Had a sneakpeak of your blog, looks really good! Will spend some time there as well!
Best regards,
Ntsako
Ntsako
Re: Orchestration job with errors in the message file completing successfully
It turns out that there is an Engine Switch that determines what constitutes a job failure, who knew.
The current default setting of the STOPERROR switch is SEVERE which means only severe errors fail the job, minor errors(!) are noted and ignored. Setting the Engine Switch to ERROR solved the issue above regarding the job completing successfully
Re: Override feature not working
Hey @appuq,
Hope all is well.
If you do get the opportunity, I would very much appreciate the recording.
Best regards,
Ntsako
Ntsako
Re: Nodes Table -- Real Example
Who dares disturb my slumber… err I mean hello Peter.
I'm, not really into sharing my examples, some of them literally took years for me to figure out.
I'm also pretty checked out of the forum these days. Hardly examples or real answers here.
But OK, I suppose…
The Classic UI, unlike the Smart UI, is very easy to add because you can easily get your own JQuery on the page.
For the Multi-Object - Custom Action I created a global appearance and put some JQuery in there that bolted on my button to the Mutli-Object menu bar.
$("#MultiDetailOperations").append( newButton );
$("#MultiDetailOperationsBottom").append( newButton );
From there I added some JavaScript to start up a WebReport when the button is clicked.
The button shows up in some places it probably shouldn't but overall its a huge win for the End-Users having a fancy button to click for Custom Business Scenarios.
Sadly the Smart UI has no such entry point in the Smart UI, unless you create your own Custom Module and Smart UI Overrides / Extensions, which is forbidden in the OT Cloud and not really a good idea in general.
The only Entry Point you get in the Smart UI is to Start a Workflow. So any kind of Bulk Custom Action has to go through a Workflow.
AnswerModules has a full range of functionality for extending the Smart UI which is OT Cloud Certified.
Good luck,
Clarkebar
Clarke
Re: Override feature not working
Hello,
I know that when overwriting a WebNodeAction for example you have to modify the _Init function to remove the original and insert your own action into the registry
Edit: I realized that you are asking about the button in the CSIDE ui, I dont know much about debugging the CSIDE
What's New with Signature Service Thrust API 26.2
Core Signature Service Thrust API 26.2 introduces several key enhancements designed to streamline integration and improve workflow efficiency.
Developers can now leverage Signing Group Support for Integrating Applications, allowing direct passing of signing groups to Core Signature from integrated applications. This eliminates the need for prior group synchronization or field mapping, simplifying the signing process for groups. Anyone from the group can sign the document and it will be considered as signed
Another significant update is Automatic Document Signing for Senders. This feature enables automated signing for eligible workflows based on predefined policies, addressing the manual effort previously required for high-volume or repetitive signing processes. This boosts efficiency while maintaining compliance.
Finally, Additional Parameters to Restrict Signer Actions on the Document Preparation Page have been added. These parameters provide more granular control, allowing document senders to disable forwarding and attachment capabilities for signers during document preparation, which helps enforce organizational security policies. These updates aim to provide more flexible and robust integration options for developers.
