...
Explanation: Enabling "Custom SQL Search" in a Lookup Control enables advanced SQL searching, allowing you to write custom queries to find records. However, the queries must begin by returning the GUID and FriendlyName of the objects to avoid compilation errors.
Common Concepts
Expand | ||
---|---|---|
| ||
Business Rules
a) To execute activities in a specific sequence b) To define the criteria for branching in the workflow based on conditions c) To add custom logic to individual workflow activities d) To determine the overall workflow design Correct Answer: b) To define the criteria for branching in the workflow based on conditions Explanation: Business Rules are used to define the criteria that dictate whether the process can follow a particular path or branch off based on varying conditions.
a) Begin, Middle, End b) Initialize, Execute, Terminate c) Evaluate, ExecuteOnIfRuleEvaluatedTrue, ExecuteOnIfNotRuleEvaluatedTrue d) Conditional, Loop, Action Correct Answer: c) Evaluate, ExecuteOnIfRuleEvaluatedTrue, ExecuteOnIfNotRuleEvaluatedTrue Explanation: Business Rule class in a workflow has three methods: Evaluate, ExecuteOnIfRuleEvaluatedTrue, and ExecuteOnIfNotRuleEvaluatedTrue, each serving a specific purpose in the workflow.
a) By clicking on the line and typing the rule directly on it b) By selecting the activity and choosing the rule from a drop-down list c) By right-clicking the line and selecting the rule from the context menu d) By dragging and dropping the rule onto the line Correct Answer: c) By right-clicking the line and selecting the rule from the context menu Explanation: Business Rules are applied to activity lines in a workflow by right-clicking the line and selecting the desired rule from the context menu. Properties
a) To define the layout and design of workflow forms b) To store data related to the workflow, including custom information c) To add predefined components like buttons and checkboxes d) To establish the workflow's execution sequence Correct Answer: b) To store data related to the workflow, including custom information. Explanation: Creating properties in Workflow Studio allows you to store data related to the workflow, including custom information that can be accessed and set throughout the workflow.
a) By clicking on the workflow canvas and selecting "Add New Property" b) By right-clicking on the parent node containing the workflow's name and selecting "Add New Property..." c) By navigating to the Bindings tab and choosing "Create New Property" d) By dragging and dropping data elements onto the workflow canvas Correct Answer: b) By right-clicking on the parent node containing the workflow's name and selecting "Add New Property..." Explanation: You can create a new property in Workflow Studio by right-clicking on the parent node containing the workflow's name and selecting "Add New Property..
a) External Storage b) Cloud Storage c) Default Storage (Internal) d) Custom Storage Correct Answer: c) Default Storage (Internal) Explanation: In most cases, the Default Storage (Internal) option is used for storing property data in Workflow Studio. Bindings
a) Custom C# code allows for faster data transfer. b) Custom C# code provides a more visual representation of data flow. c) Custom C# code offers greater flexibility and control over data binding. d) Custom C# code is the only method for binding in Workflow Studio. Correct Answer: c) Custom C# code offers greater flexibility and control over data binding. Explanation: Writing custom C# code for binding provides greater flexibility and control over the data binding process, making it a valuable option. 2. When binding data from a lookup control to a form in Workflow Studio, what property should be dragged and dropped in the Binding Mapper? a) SelectedValueAsComponent b) Output c) TargetPerson d) Input/Output Node Correct Answer: a) SelectedValueAsComponent Explanation: In the Binding Mapper, you should expand the tree control for the lookup, then expand its Output node of a Lookup Control, and select the SelectedValueAsComponent property to drag and drop it onto the form's TargetPerson or related property. Some Common Event Handlers
a) Completed b) Exception c) Idle d) Resume Correct Answer: c) Idle Explanation: The "Idle" event handler in EmpowerID is invoked when a workflow enters an idle or suspended state, as mentioned in the provided information.
a) After the activity code execution b) When the workflow enters an idle state c) Before the activity code execution d) When a runtime error occurs Correct Answer: c) Before the activity code execution Explanation: The "Before Execute" event handler of an activity in EmpowerID is invoked before the activity code execution, allowing you to perform tasks or actions before entering the activity, as stated in the provided information. Set Data Code and Get Data Code Methods
a) Set Data Code and Get Data Code methods create separate classes for each event. b) Set Data Code and Get Data Code methods are less efficient. c) Set Data Code and Get Data Code methods consolidate all code in one place. d) Set Data Code and Get Data Code methods require more debugging. Correct Answer: c) Set Data Code and Get Data Code methods consolidate all code in one place. Explanation: The provided information states that Set Data Code and Get Data Code methods consolidate all code in one class or place, making it easier to debug and read compared to Before Execute and After Execute event handlers.
a) After your activity executes b) Before your activity executes c) After a runtime error occurs d) During an idle state of the workflow Correct Answer: b) Before your activity executes Explanation: The SetDataCode Event in EmpowerID runs before your activity executes and is typically used to initialize or set your activity properties, as mentioned in the provided information. Common Workflow Activity Types
a) Form activities display messages to users. b) Form activities capture and pass user input to other workflow activities. c) Form activities execute custom code using the ExecuteCode event handler. d) Form activities determine if the current user has necessary workflow authorization. Correct Answer: B Explanation: Form activities are used to capture and pass user input to other activities in the workflow. They generate form fields as "dependency properties" that can capture user input.
a) To execute custom code using the ExecuteCode event handler. b) To display confirmation messages with "Yes" and "No" buttons to users. c) To protect the execution of "action" code for an activity. d) To execute operations in parallel. Correct Answer: b) Explanation: Confirm activities are used to display confirmation messages with "Yes" and "No" buttons to users. They are often used in situations where resources are being deleted, and user confirmation is required.
a) Name, Description, Enabled b) Message, MessagesList, WaitForResponse c) Rule, Name, Description d) TargetRBACObjects, ShowAttributeModificationSummaryOnApproval, Password Correct Answer: c) Explanation: The key properties of System If Else activities are Name, Description, and Enabled. These activities are used to apply conditions or rules to parallel branches in workflows. Debugging Workflows in Workflow Studio
a) Start Visual Studio and open the workflow file. b) Select "Hidden Items" in the View menu. c) Attach to all w3wp.exe processes in the Available Processes pane. d) Click OK in the Inconsistent Line Ending dialog. Correct Answer: c) Explanation: To enable debugging for a workflow using Visual Studio, you should attach to all w3wp.exe processes in the Available Processes pane in Visual Studio. This allows you to debug the workflow process.
a) To enable debugging for all types of exceptions. b) To disable debugging for runtime exceptions. c) To configure specific exception handling for the workflow. d) To skip the workflow's breakpoints during debugging. Correct Answer: a) Explanation: Selecting "Common Language Runtime Exceptions" in the Exception Settings of Visual Studio enables debugging for all types of runtime exceptions. This ensures that you can observe and debug any exceptions that occur during workflow execution. |