Create a code to identify the workflow event, add the workflow event to the library, create an event that the workflow event subscribes to, raise the event, and then subscribe to the event and implement the workflow event.

1. Create a new codeunit that will be used for new workflow events. Name it to reflect that it is used to identify the new workflow event, such as My Workflow Events. For more information, see How to: Create a Codeunit.

2. Create a global function in the codeunit. Name the function to reflect that it is used to identify the workflow event, such as MyWorkflowEventCode. For more information, see How to: Add a Function to a Codeunit.

3. Open the C/AL Locals window to add a local return value. For more information, see C/AL Locals.

4. On the Return Value tab, fill the fields as described in the following table.

   Return Type	Length
   Code	128

1. Create another function in the codeunit. Name it to reflect that it is used to add the workflow event to the library, such as AddMyWorkflowEventsToLibrary.

2. In the Properties window, fill the fields as described in the following table.

   Property	Value
   Event	Subscriber
   EventPublisherObject	Codeunit Workflow Event Handling
   EventFunction	OnAddWorkflowEventsToLibrary

3. Open the C/AL Locals window to add a local variable.

4. On the Variables tab, fill the fields as described in the following table.

   Name	DataType	Subtype
   WorkflowEventHandling	Codeunit	Workflow Event Handling

5. In the function, write code that handles the event, such as the following code.

   	Code kopieren
   WorkflowEventHandling.AddEventToLibrary(MyWorkflowEventCode,DATABASE::”Purchase Header”,’A purchase header is posted.’,0,FALSE);

1. Create a function in the codeunit where you want to raise the event, such as the Purch.-Post codeunit. Name the function to reflect that it is used as the publisher event, such as OnAfterPostPurchaseHeader.

2. In the Properties window, fill the fields as described in the following table.

   Property	Value
   Event	Publisher
   EventType	Select the event type that is relevant for the workflow event, such as Integration. For more information, see Event Types.

3. Open the C/AL Locals window to add a local parameter.

4. On the Parameters tab, fill the fields as described in the following table.

   Name	DataType	Subtype
   Purchase Header	Record	Purchase Header

For more information, see Publishing Events.

1. Go to the code in your solution where you want to raise the event, such as the Purch.-Post codeunit.

2. In the function, write code that raises the event, such as the following code.

   	Code kopieren
   OnAfterPostPurchaseHeader(PurchaseHeader);

For more information, see Raising Events.

1. Create another function in the codeunit where you created the identification code, MyWorkflowEventCode. Name the function to reflect that it is used to subscribe to and implement the workflow event, such as RunWorkflowOnAfterPostPurchaseHeader.

2. In the Properties window, fill the fields as described in the following table.

   Property	Value
   Event	Subscriber
   EventPublisherObject	Select the object that contains the definition of the added event, such as the Purch.-Post codeunit.
   EventFunction	OnAfterPostPurchaseHeader

3. Choose Yes to overwrite your local parameters with the event parameters.

4. Open the C/AL Locals window to add a local variable.

5. On the Variables tab, fill the fields as described in the following table.

   Name	DataType	Subtype
   WorkflowManagement	Codeunit	Workflow Management

6. In the function, write code that handles the event, such as the following code.

   	Code kopieren
   WorkflowManagement.HandleEvent(MyWorkflowEventCode,PurchaseHeader);

Another task that you can perform at this point is to specify which filter fields appear in the Ereignisbedingungen window. For more information, see Dynamische Anfrageseite - Entität.

For more information, see Subscribing to Events.

You have now created a new workflow event. Proceed to create a new workflow response that relates to the workflow event.

Create a code to identify the workflow response, add the workflow response code to the library, implement the workflow response, and then enable that the workflow response can be executed.

1. Create a new codeunit that will be used for the new workflow responses. Name it to reflect that it handles your new responses, such My Workflow Responses.

2. Create a function in the codeunit. Name the function to reflect that it is used to identify the workflow response, such as MyWorkflowResponseCode.

3. Open the C/AL Locals window to add a local return value.

4. On the Return Value tab, fill the fields as described in the following table.

   Return Type	Length
   Code	128

1. Create another function in the codeunit. Name it to reflect that it is used to add the workflow response to the library, such as AddMyWorkflowResponsesToLibrary.

2. In the Properties window, fill the fields as described in the following table.

   Property	Value
   Event	Subscriber
   EventPublisherObject	Codeunit Workflow Response Handling
   EventFunction	OnAddWorkflowResponsesToLibrary

3. Open the C/AL Locals window to add a local variable.

4. On the Variables tab, fill the fields as described in the following table.

   Name	DataType	Subtype
   WorkflowResponseHandling	Codeunit	Workflow Response Handling

5. In the function, write code that registers the response, such as the following code.

   	Code kopieren
   WorkflowResponseHandling.AddResponseToLibrary(MyWorkflowResponseCode,DATABASE::"Purchase Header",'Send a notification.','GROUP 0')

   Hinweis
   In the “To add a new workflow response option” procedure, you will change the GROUP value to, for example, 50000.

1. Create another function in the codeunit. Name it to reflect that it is used to implement the workflow response, such as MyWorkflowResponse.

2. Open the C/AL Locals window to add a local parameter.

3. On the Parameters tab, fill the fields as described in the following table.

   Name	DataType	Subtype
   Purchase Header	Record	Select the relevant record, such as Purchase Header table.

4. In the function, write code that handles the response, such as the following code.

   	Code kopieren
   CODEUNIT.RUN(CODEUNIT::"Purch.-Post",PurchaseHeader);

1. Create another function in the codeunit. Name it to reflect that it is used to enable the new workflow response to be executed alongside existing workflow responses, such as ExecuteMyWorkflowResponses.

2. In the Properties window, fill the fields as described in the following table.

   Property	Value
   Event	Subscriber
   EventPublisherObject	Codeunit Workflow Response Handling
   EventFunction	OnExecuteWorkflowResponse

3. Choose Yes to overwrite your local parameters with the event parameters.

4. In the function, write code that enables the response, such as the following code.

   	Code kopieren
   IF WorkflowResponse.GET(ResponseWorkflowStepInstance."Function Name") THEN CASE WorkflowResponse."Function Name" OF MyWFResponseCode: BEGIN MyWorkflowResponse(Variant); ResponseExecuted := TRUE; END; END;

1. Open table 1523, Workflowschritt-Argument, in design mode.

2. Add a field that reflects your new response option, such as My New Response Option. For more information, see How to: Add Fields to a Table.

3. Open page 1523, Workflowreaktionsoptionen, in design mode.

4. Add a group and a control for the new field.

5. For the Visibility property of the group, enter, for example, "Response Option Group" = 'GROUP 50000'.

6. Open the AddMyWorkflowResponsesToLibrary function.

7. In the function code, change ‘GROUP 0’ to ‘GROUP 50000’.

8. To make sure that the new workflow response is updated, delete the Send a notification. response from the Workflowreaktion table.

   To use the new option in the MyWorkflowResponse function, proceed to add a local parameter and a local variable.

9. Open the C/AL Locals window to add a local parameter and a local variable.

10. On the Parameters tab, fill the fields as described in the following table.

    Name	DataType	Subtype
    WorkflowStepInstance	Record	Workflow Step Instance

11. On the Variables tab, fill the fields as described in the following table.

    Name	DataType	Subtype
    WorkflowStepArgument	Record	Workflow Step Argument

12. In the function, write code that enables the response, such as the following code:

    	Code kopieren
    IF WorkflowStepArgument.GET(WorkflowStepInstance.Argument) THEN;

    You now have access to your new field on the Workflowschritt-Argument table that you can use as a workflow response option.

13. In the ExecuteMyWorkflowResponses function, make the following code change:

    Change from this code: MyWorkflowResponse(Variant);

    Change to this code: MyWorkflowResponse(Variant,ResponseWorkflowStepInstance);

You have now created the actual workflow event and response. Proceed to perform various tasks that enable them to be used in workflows.

Add new workflow event/response combinations to the WF-Ereignis-/Reaktionskombination table so that they appear correctly in the Workflowereignisse and Workflowreaktionen windows.

1. Open the codeunit that you created in the “To create a workflow response” procedure, My Workflow Responses.

2. Create another function in the codeunit. Name it to reflect that it is used to add the workflow event/response combinations to the WF-Ereignis-/Reaktionskombination table, such as AddMyWorkflowEventResponseCombinationsToLibrary.

3. In the Properties window, fill the fields as described in the following table.

   Property	Value
   Event	Subscriber
   EventPublisherObject	Codeunit Workflow Response Handling
   EventFunction	OnAddWorkflowResponsePredecessorsToLibrary

4. Choose Yes to overwrite your local parameters with the event parameters.

5. Open the C/AL Locals window to add two local variables.

6. On the Variables tab, fill the fields as described in the following table.

   Name	DataType	Subtype
   MyWorkflowEvents	Codeunit	My Workflow Events
   WorkflowResponseHandling	Codeunit	Workflow Response Handling

7. In the function, write code that registers event/response combinations that you want to support in your application, using a CASE statement, such as the following code.

   	Code kopieren
   CASE ResponseFunctionName OF   MyWorkflowResponseCode:     WorkflowResponseHandling.AddResponsePredecessor(MyWorkflowResponseCode,MyWorkflowEvents.MyWorkflowEventCode); END;

You can also do this work from the user interface. For more information, see Workflowereignis-/Reaktionskombinationen.

Add new workflow event/event combinations to the WF-Ereignis-/Reaktionskombination table so that they workflow events appear in the correct hierarchy in the Workflowereignisse window.

1. Open the codeunit that you created in the “To create a workflow event” procedure, My Workflow Events.

2. Create another function in the codeunit. Name it to reflect that it is used to add the workflow event hierarchies to the WF-Ereignis-/Reaktionskombination table, such as AddWorkflowEventHierarchiesToLibrary.

3. In the Properties window, fill the fields as described in the following table.

   Property	Value
   Event	Subscriber
   EventPublisherObject	Codeunit Workflow Event Handling
   EventFunction	OnAddWorkflowEventPredecessorsToLibrary

4. Choose Yes to overwrite your local parameters with the event parameters.

5. Open the C/AL Locals window to add a local variable.

6. On the Variables tab, fill the fields as described in the following table.

   Name	DataType	Subtype
   WorkflowEventHandling	Codeunit	Workflow Event Handling

7. To make sure that the new workflow event is updated, delete the A purchase header is posted. event from the Workflowereignis table.

8. In the function, write code that registers event hierarchies that you want to support in your application, using a CASE statement, such as the following code.

   	Code kopieren
   CASE EventFunctionName OF   MyWorkflowEventCode:     WorkflowEventHandling.AddEventPredecessor(MyWorkflowEventCode,WorkflowEventHandling.[your desired predecessor event code]); END;

You can also do this work from the user interface. For more information, see Workflowereignishierarchien.

Workflows events can be executed on different types of records. To keep track of these, you must define relations between the involved records.

1. Open the codeunit that you created in the “To create a workflow event” procedure, My Workflow Events.

2. Create another function in the codeunit. Name it to reflect that it is used add workflow table relations in the Workflow - Tabellenrelation table, such as AddWorkflowTableRelationsToLibrary.

3. In the Properties window, fill the fields as described in the following table.

   Property	Value
   Event	Subscriber
   EventPublisherObject	Codeunit Workflow Event Handling
   EventFunction	OnAddWorkflowTableRelationsToLibrary

4. Open the C/AL Locals window to add a local variable.

5. On the Variables tab, fill the fields as described in the following table.

   Name	DataType	Subtype
   WorkflowSetup	Codeunit	Workflow Setup

6. To make sure that the new workflow event is updated, delete the A purchase header is posted. event from the Workflowereignis table.

7. In the function, write code that registers table relations that you want to support in your application, such as the following code.

   	Code kopieren
   WorkflowSetup.InsertTableRelation(DATABASE::”Purchase Header”,1,DATABASE::”Approval Entry”,2);

You can also do this work from the user interface. For more information, see Workflow - Tabellenrelationen.

Add a FactBox to relevant pages so that users can view when and how the new workflow event and response participate in workflows for records shown on the page.

1. Open, in design mode, the page from where users need to see related workflows that use the new workflow event and response.

2. Add a FactBox. Name it WorkflowStatus. For more information, see How to: Add a FactBox to a Page.

3. Open the C/AL Globals window to add a global variable.

4. On the Variables tab, fill the fields as described in the following table.

   Name	DataType	Subtype
   ShowWorkflowStatus	Boolean

5. To make the FactBox visible, in the Properties window, fill the fields as described in the following table.

   Property	Value
   Visible	ShowWorkflowStatus

6. On the page, add the following code to the OnAfterGetCurrentRecord function to make the FactBox find the workflow that relates to the record.

   	Code kopieren
   ShowWorkflowStatus := CurrPage.WorkflowStatus.PAGE.SetFilterOnWorkflowRecord(RECORDID);

You have now enabled a new workflow scenario by implementing the required workflow event and response in the application code. The workflow administrator can now select the workflow event and workflow response from the Workflow window to define new or edit existing workflows. For more information, see So wird's gemacht: Erstellen von Workflows.

Aufgaben

Konzepte