Workflow uses the Document type message property
The message content of the workflow, the simplest of which is text, or static HTML text, but can be met with limited circumstances.
A lot of times the workflow is going to show a list, not sure how many rows it has, so it can't be set in advance, and it's not possible to enumerate all the variables.
This is the time to use the dynamic message content, which is the message property of the document type described in this article.
Development steps
Define a stored procedure to dynamically get the content of a message
Oracle Workflow Developer ' s Guide 6-12
PROCEDURE get_request_msg(document_id IN VARCHAR2,
display_type IN VARCHAR2,
document IN OUT NOCOPY VARCHAR2,
document_type IN OUT NOCOPY VARCHAR2)
- DOCUMENT_ID: Pass a unique identifier, as long as you can get the dynamic content you want based on this ID
- Display_type:text/html (see DG for other types)
- Document: This example is the content of the HTML, in the process to spell up can
- Document_type:text/html (see DG for other types)
Create attribute (here I am the local attribute of the definition, not the global property of the workflow, because this property does not need to be assigned globally, is dynamically fetched)
- Set the type of the property to document
- Set the value of the default value to:
plsql:[程序包名.]过程名/document_id
Grammar:plsql:<procedure>/<document_identifier>
Attention
- Because it is a dynamic message, the background process is called every time it is opened, and if the approval process requires documentation, it is best to make the appropriate logic.
- Cancellation of the process is best not often modified, if modified, also to be selected in the current notification less time update, because the database updates the package, in the workflow
Will not be reflected in the first time, there will be no package found in the case.
From for notes (Wiz)
"EBS WORKFLOW" workflow uses the document type's message properties