Thursday, July 7, 2016

K2 Interview Questions: Workflows, Part 1 (Advance)

What is IPC event wizard?
  • The IPC (The Inter Process Communication) event wizard is normally used to implement a Parent-Child workflow or sub-workflow requirement.
  • Also it is useful when you want to split a larger workflow into sub-processes, when you have processes that are generically re-usable, or when you want to start multiple instances of a child workflow from a parent workflow.
  • You can use it to set Folio, Originator, and data field values for a Child workflow as part of the wizard.
  • There are two options while configuring the call to the child process
    Synchronous: Parent workflow waits for Child workflow to complete.
    Asynchronous: 'fire-and-forget' style, in which the Parent workflow continues immediately after starting the Child workflow.
  • Use advanced destination rules (Plan per Slot, No Destinations) to allow one Parent workflow to start multiple Children
What are different activity planning options in Advance destination rule? and explain them.
There are three main Activity Planning options: Plan Just Once, Plan Per Destination, and Plan Per Slot.

           Plan Just Once : 
  • This default option. K2 will execute the events in the Activity prior to the Client Event just one time, regardless of how many destinations or slots have been defined. The events after the Client event will be executed each time a user completes a task. This is the default behavior for Activities.
  • This option is most appropriate for high-volume scenarios where a large group gets the task but only one user will ever need to open the task.
  • When this option is selected, there is only one activity instance, which is shared amongst all destinations for the task.

    Plan per destination:
  • This approach is most often used when more than one person will open the task, and you need to capture input from each user into the same activity datafields.
  • K2 creates separate copies of the Activity Instance for each destination

    Plan per destination – All at Once :
  • K2 will execute the events in the activity for each destination in the activity in parallel fashion. Each event in the activity is repeated for each destination, and then K2 moves on to the next event in the activity and repeats that event for each destination.
  • This planning option specifies that all destinations will get the task at the same time (Parallel). Any one of the destination users can open the task and complete it. If any of the outcomes are true for the activity, the other copies of the task are removed from the other user’s task lists, and K2 completes the activity.
  • Plan per destination – One at a Time : K2 will execute the events in the activity for each destination in the activity in serial fashion. K2 starts with the first destination and executes the Events in the activity once for that destination. If the Outcome is false, K2 moves on to the second destination and then executes the events in sequence for the second destination. This is repeated for each destination in the activity until the Outcome succeeds or no more destinations are available.

    Plan per slot – (no destinations)
  • This setting is normally used for activities that only contain server events when you want to repeat the events in the activity N-number of times for each slot in the activity. 
  • It is similar to the Plan Per Destination – All at Once setting except that K2 does not use the Destinations to determine how many times to execute the events but rather the number of slots specified on the next page of the Destination Rule wizard.
What is use of Update Design Templates in K2 visual studio workflows?
The purpose of this tool is to apply enhanced code templates when you have upgraded your K2 environment to a newer version of the platform.The Update Design Templates command in the K2 design tools will wipe out any customizations you may have applied because it restores the original templates for all items and will undo any customization.

What event is use to write a code in workflow?
Default server event wizard is used to write a code in workflow. It is only available in K2 for Visual studio.

How can be method be called from custom assembly or service?
There are alternative approaches to using code in your workflows: 
1. You can add reference to the assembly and call method in a class adding using namespace reference in default server code event
2. You can use the Code Reference Event to call methods for referenced assemblies and services.
When a workflow must interact with a system that is not exposed as a K2 SmartObject, but you do not wish to write code, the code reference event comes to the rescue. This event can be used to call methods on web services (asmx), WCF services and assemblies (.NET and COM dll’s).
3. If you need to call the same assembly/Service multiple times, it is recommended to expose that assembly/Service as a SmartObject.
  • By using one of the available EndPoint Service Brokers,
  • By writing a custom Broker that exposes the necessary functions. This will allow you (and other designers) to call the methods in the Service/Assembly easily without having to write code.

What is Asynchronous server event?
Asynchronous Server Events are used when you want the server event to wait for an external system to call back. The external system will use a serial number to complete the task and tell the K2 server event to continue.

What are the different places in workflow you can enable and handle exception?
You can handle the exception at event, activity, line, escalation rule, escalation action and at process level

All K2 Interview Questions

No comments:

Post a Comment