Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
basic
Manage
Activity
Members
Code
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Deploy
Releases
Model registry
Analyze
Contributor analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
xrm
basic
Commits
51704808
Commit
51704808
authored
4 years ago
by
Sebastian Listl
Committed by
Sebastian Pongratz
4 years ago
Browse files
Options
Downloads
Patches
Plain Diff
WorkflowSignalSender variables added to method arguments
(cherry picked from commit
e972c8fe
)
parent
15d9fd4e
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
process/Workflow_lib/process.js
+15
-12
15 additions, 12 deletions
process/Workflow_lib/process.js
with
15 additions
and
12 deletions
process/Workflow_lib/process.js
+
15
−
12
View file @
51704808
...
...
@@ -128,33 +128,36 @@ WorkflowSignalSender.EVENT_DELETE = function ()
* Adds an entry to a context-variable that tells a insert happened. The variable is then checked by WorkflowSignalSender.doInsertedOrUpdated,
* where the actual logic is executed. The reason for this approach is that 'inserted' signals should be thrown after the insert finished.
*
* @param {String} pTargetId uid of the inserted dataset
* @param {String} pTargetContext context of the inserted dataset
* @param {Object} [pVariables] variables to set
* @param {String} [pTargetId=$sys.uid] uid of the inserted dataset
* @param {String} [pTargetContext=current context] context of the inserted dataset
*/
WorkflowSignalSender
.
inserted
=
function
(
pTargetId
,
pTargetContext
)
WorkflowSignalSender
.
inserted
=
function
(
pVariables
,
pTargetId
,
pTargetContext
)
{
WorkflowSignalSender
.
eventHappened
(
WorkflowSignalSender
.
EVENT_INSERT
(),
pTargetId
,
pTargetContext
);
WorkflowSignalSender
.
eventHappened
(
WorkflowSignalSender
.
EVENT_INSERT
(),
pTargetId
,
pTargetContext
,
pVariables
);
}
/**
* Adds an entry to a context-variable that tells a update happened. The variable is then checked by WorkflowSignalSender.doInsertedOrUpdated,
* where the actual logic is executed. The reason for this approach is that 'updated' signals should be thrown after the update finished.
*
* @param {String} pTargetId uid of the updated dataset
* @param {String} pTargetContext context of the updated dataset
* @param {Object} [pVariables] variables to set
* @param {String} [pTargetId=$sys.uid] uid of the inserted dataset
* @param {String} [pTargetContext=current context] context of the inserted dataset
*/
WorkflowSignalSender
.
updated
=
function
(
pTargetId
,
pTargetContext
)
WorkflowSignalSender
.
updated
=
function
(
pVariables
,
pTargetId
,
pTargetContext
)
{
WorkflowSignalSender
.
eventHappened
(
WorkflowSignalSender
.
EVENT_UPDATE
(),
pTargetId
,
pTargetContext
);
WorkflowSignalSender
.
eventHappened
(
WorkflowSignalSender
.
EVENT_UPDATE
(),
pTargetId
,
pTargetContext
,
pVariables
);
}
/**
* @param {String} pTargetId uid of the deleted dataset
* @param {String} pTargetContext context of the deleted dataset
* @param {Object} [pVariables] variables to set
* @param {String} [pTargetId=$sys.uid] uid of the inserted dataset
* @param {String} [pTargetContext=current context] context of the inserted dataset
*/
WorkflowSignalSender
.
deleted
=
function
(
pTargetId
,
pTargetContext
)
WorkflowSignalSender
.
deleted
=
function
(
pVariables
,
pTargetId
,
pTargetContext
)
{
WorkflowSignalSender
.
eventHappened
(
WorkflowSignalSender
.
EVENT_DELETE
(),
pTargetId
,
pTargetContext
);
WorkflowSignalSender
.
eventHappened
(
WorkflowSignalSender
.
EVENT_DELETE
(),
pTargetId
,
pTargetContext
,
pVariables
);
}
/**
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment