Al: Need access to workflow template functions

[MikeGlue]

Need access to the following in order to create workflow templates:

Codeunit 1502 (Workflow Setup)

• MarkWorkflowAsTemplate
• InsertWorkflowTemplate
• InsertEntryPointEventStep
• InsertStep
• InsertResponseStep
• GetSequenceNumber
• SetCustomTemplateToken

Also....why does InsertWorkflowTemplate not call MarkWorkflowTemplate directly? If it did, then we don't need access to the MarkWorkflowAsTemplate function.

[StHillmann]

@DominikDitoIvosevic

What about this issue? You know why it is closed?
From my point of view #929 does not fix this issue!?!

The methods are still "internal" so we cannot use it for creating workflow templates without the need to duplicate the standard ones...

Additionally to the named methods above, we need to be marked as "external":

• InsertEventArgument

[Djordje-Arsic]

@DominikDitoIvosevic @StanislawStempin

Same question here, this issue is open for a long time.

Other than what @StHillmann asked for, I need following procedures marked as "external":

• PopulateWorkflowStepArgument
• Encode

[JesperSchulz]

Wow! This issue has been around for a while! Let me look into it!

[JesperSchulz]

All the requested functions in this issue are local functions with rather simple logic in it. Ideally, we would like to avoid exposing local functions, as that reduces our possbilities to refactor and change our code. If we would expose all requested local functions in this codeunit, our possibilities to change any of the logic in the workflow functionality would be severly reduced, if we don't want to make any breaking changes (which we don't). Please allow me to look closer into, why it would be necessary for you to have access to these functions. I will get back to you later today.

[MikeGlue]

Basically, to sum things up, if you want to extend and add new workflows, complete with new workflow templates, the functions that I identified are all needed. I would hope that we aren't expected to copy all of those into our solutions. Perhaps a nice facade wrapper or something can be done to allow us to achieve what we need. The workflow engine is great, but extending it to our own entities, etc. is key.

[JesperSchulz]

A nice facade would be prefereable here, but since we're a little low on time, we've decided to go for the "quick and dirty" solution, which is to expose all of the functions you request ;-) I will process this request later today!