Pega Course Details. By Besant Technologies. Course Name. Pega. Category. BPM Tool(Business Process Management Tool). Venue. Besant Technologies. learn pega prpc through online for more details call: [email protected] Communities · Pega Academy; Course material pdf PRPC Fast Track Have a look at the first lessons, you can now download the PDF.
|Language:||English, Spanish, Dutch|
|ePub File Size:||17.50 MB|
|PDF File Size:||17.80 MB|
|Distribution:||Free* [*Regsitration Required]|
Pega Training- The best Pega PRPC Tutorial ever . Can I get Training materials like pdf, ppt, and user guide on Wikipedia for PEGA?. Pega Tutorial PDF - Download as PDF File .pdf), Text File .txt) or read online. Pega Tutorial PDF. DCO Introduction – Pega PRPC v5. Uploaded by. Rajeev. pega tutorial ppt pega tutorial point pega prpc tutorial pdf pega 7 tutorials pega tutorial ebooks pega 7 tutorial pdf pega tutorial videos pega training videos.
Configure three connectors from the decision shape. View properties for the End shape in the process diagram. A possible exception might be a situation where the hierarchy was built incorrectly. Gaurav Lakshkar. This document does not imply any commitment to offer or deliver the products or services described. Click inside the Use Validate field and then use the down-arrow to select ValidEmailAddress from the available validation types.
This document is the property of: Pegasystems Inc. Understanding Inheritance Software Version 4. May 22, Inheritance paths Rule resolution is the process used to identify which rules are applied to a specific business decision. Enabling Rule Resolution on rules Rules. At execution. Models RuleObj-Model. Process Commander dynamically selects the right process or business rule depending on the business purpose. This document is not an in-depth exploration of Rule Resolution itself.
Process Commander provides flexibility that is otherwise impossible except with the alternative of applying rules specified in code. Through dynamic rule selection. Not all rules are rule-resolved. The ability of a particular rule type Activity.
RuleSet and version. Properties Rule-Obj-Property. Rule Resolution must be enabled on the class definition. Streams Rule-Stream. When this box is checked. The features are described below so that developers may understand the functionality available for each Rule. The different checkboxes control different functionality for resoution. This section of the class form enables rule resolution for the rule. These features are contained in two sections on the Class form: This option is only available for classes which start with Rule-.
If checked. Allow multiple versions with the same key values Rule Resolution This is the most important choice for Rule Resolution. Rule Resolution is used: Overview of Rule Resolution When classes are defined.
If this box is not checked. If the Allow multiple versions with the same key values box is not checked. Declarative rules may not use Circumstances. Class Inheritance and Rule Resolution As stated above. For rules which are defined on other rules such as Activities. Rule Resolution will be used to open instances of this class. Use class-based inheritance to arrive at the correct rule to execute This field defines how inheritance through the class hierarchy affects this rule.
It is possible for Rules to have this box checked and not have the Use classbased inheritance to arrive at the correct rule to execute box checked. For this functionality. Circumstances and Circumstance Dates may not be used with this rule. Allow rules that are only valid for a certain period of time Date Range Availability This checkbox allows the rule to be qualified by a Date Range. For example. Details on the functionality enabled by this checkbox are in the next section.
Declarative rules also may not use Date Ranges. If only Allow multiple versions with the same key values is checked. Allow selection of rules based on property values Circumstance Qualified This checkbox allows the rule to be Circumstance-qualified. Overview of Rule Resolution There are some types of rules.. In the above example. Decision Tables. Instances of this rule will not be defined on any classes. Other rules. The Class Inheritance section of the class form defines the class hierarchy and inheritance for this class.
Process Commander will search other classes. When a particular activity or property or other such rule is called during processing. If the rule is not present in that class. Inheritance Inheritance For rules such as activities which are defined on classes. This section describes the paradigm used to search the class hierarchy during rule resolution.
Note that pattern inheritance will cause the system to search all the way through the class pattern hierarchy before checking directed inheritance.
Directed Inheritance Directed inheritance allows the user to specify or direct from what classes the current class may inherit. It is possible to independently change the definition of Display in any or all of these other classes. A directed inheritance class is required for each class being defined.
Rule Resolution will search for the activity Display. Pattern inheritance is always checked first. If this box is checked. Inheritance Find by name first Pattern — determines pattern inheritance. Directed inheritance classes do not have to have the same name as the current class. By default. The field will default to the pattern class parent. Parent class to inherit from Directed — determines directed inheritance.
This field holds the immediate parent. Pattern inheritance should remain enabled checked. Inheritance Important: The system will not prevent users from creating classes with inheritance that is circular.
If this kind of circular inheritance does happen. Although pattern inheritance allows the system to search through an entire chain of classes. If a match is not found. Directed inheritance is evaluated on a class-by-class basis. If Pattern inheritance is enabled. A possible exception might be a situation where the hierarchy was built incorrectly. If the activity were not found there.
See Scenario 1 in the example. Inheritance Example: Inheritance paths The following classes are in the system: There are several paths that rule resolution for this Activity could take.
Inheritance Inheritance is set up for the above diagram by checking inheritance boxes on Class forms: Class On Class Form: In the above setup. Inheritance As stated above. Save updates and then Close the Screen Candidate section. Optional Exercise Use this optional exercise to look in the Application Explorer for the data properties and user interface sections that have been created for the Candidate case. Adding a Repeating Layout Scenario When the candidate applies for the job they must include any professional work experience that would help the recruiters to consider them for the open position.
This information should include the company name, job title, and both starting and ending date. Similarly, the candidates should indicate their educational background in terms of institution name, highest grade achieved, and year of graduation. Approach Use the stage designer approach that we learned in the lesson to create new repeating layouts in the Collect professional info and Collect educational info steps.
For the Collect Professional Information action, create a page list named Work History with properties from the table below. For the Collect Educational Information action, create a page list named Educational Background with properties from the table below. Click the Configure process detail link in the Case Designer to open the outline view. New fields default to Text in the Configure form dialog. Select Object to generate a property of type Page.
Select List of objects to generate a Page List. Procedure We have seen how you can configure a form for an assignment step by going to the process outline and while testing a case. In this exercise, we will select Configure form from the step menu in the case designer. Open the Candidate case in the Case Designer, if necessary. Open the step menu for the Professional Info step and select Configure form. In Form configuration, enter Work History and select List of objects to generator a page list type property.
In the first field for Work History, enter Company Name. Click Add field to list three times and then enter the remaining field names Job Title, Start Date and End Date and property modes from the table in the Approach section of this exercise.
Ensure that all of your fields have been entered correctly and that Work History is a List of objects before saving your new page list. Click Save to close the Form configuration dialog. Save the updates to the case type.
You may need to Refresh the Application Explorer to see the new page list. Test the new UI by running the process to create a new case. Return to the Candidate case and create a form for the Educational Info step in the Collect Information stage.
Open the Form configuration dialog using any of the ways listed in the Hints section. Using instructions supplied in steps , create a page list named Educational Background with fields Institution Name, Highest Grade Achieved and Year of Graduation listed in the Educational Background table in the Approach section of this exercise.
After checking to be sure that your data types are correct, click Save to close the Form configuration dialog and Save updates to the case type. Run the process to create a case so you can view the updated UI section.
Adding a New Control on an Existing Field Scenario The business architect reviewed the screens that we have created so far and gave us a few additional requirements. The first request is that we add a new field which permits the capturing of candidate skills information. The second request is to increase the size of the current Screener Comment field. It is currently too small and does not allow for the capture of a significant amount of feedback from the recruiters.
They would like to have this fixed by providing the operator with an option to enter a few lines of feedback that can be easily read.
Approach In the professional information step of the collect information stage, add a new property named Skills using the Stage Designer. This property can be defined as text which will use pxTextinput. Make sure all relevant options in the toolbar are selected. Hints The section can be accessed by opening the process in outline view. Add the property for Skills in the step before accessing the section. The product creates the property with a text input field, open the properties panel and change control to use RichTextEditor RTE.
Configure the parameters for RTE in the properties panel of the field. Procedure We have created a form to enter candidate professional information, but need to add a field for Skills. Begin by creating a Skills property and then add it to the Professional Information section.
Save and then Close the property rule form for the new Skills property. Name the property Skills. Use property defaults. Open the Candidate case in the Case Designer and then click Configure process detail under the Collect Information stage to open the stage in the Process Outline.
Refresh the Application Explorer and look for your new property. Select the Professional Info step in the stage steps. When the section opens.
Click the handle of the new dynamic layout and drag it below the work history. Since Skills is not a list object. Set layout type to Dynamic Layout.
Select Layout from the Layout menu. Click in the Skills cell and then click the View Properties icon form. Click handle of the Skills property and drag it into the new layout.
Change the control from Text input to Rich text editor. After selecting the control. Open the Qualify Stage in the process outline. Close the Section tab. Click OK to close the layout cell properties form and then Save changes to the section.
Select the Screen Candidate step and then click Open section. Using the instruction beginning in step To allow more space in the screener comments.
The list of values is stored as local list in the property definition. Hints To edit cell or section properties using the UI Inspector.
The radio button also exists in the basic palette www. Run the process to create a new case and then do the following: While the applicable form is displayed.
The dropdown exists in the basic palette. Hover over the cell or section that you want to change until the Information Panel displays and then click the blue rule property link for the cell or section. Create a new Candidate case using either the Run button or the Create menu. Is Not a Fit for the Role from the Approach section of this exercise.
Requires Additional Training. In the property rule edit form. Save changes and then return to the open case. Hover over the Screener Feedback field until the Information Panel displays and then click the blue ScreenerFeedback property link for the Cell. Submit user input for each process step until you reach the Screen Candidate step. When table value fields open up. While the Screen Candidate form is displayed.
Click OK to close the layout cell properties dialog. Click inside the Screener Feedback cell and then click the View Properties icon to view layout cell properties. Hover over the group of fields that comprise the Screen Candidate section until the Information Panel displays and then click the blue ScreenCandidate property link for the Section.
Click the change link in the layout cell properties form and then select Dropdown from the basic input group. After returning to the Screen Candidate layout section form. Refresh the open case or create a new case to test changes made to the Screen Candidate user interface. Save the Screen Candidate section changes and then Close the tab. Save updates to the Candidate case type. Click the change link in the layout cell properties form and then select Radio buttons from the basic input group.
Click Open Section. Identifying Mandatory Fields Scenario When a candidate is entering an application. To make Email a required field. In that case. From the Case Designer landing page for the Candidate case. If you have opened and saved a section the Configure form link may no longer be visible. If you have already made changes in the section rule. Create a new case to test changes made to the case type.
Be sure to save any updates made to sections and then to the Candidate case type. Save changes to the section and then Close the section tab. Email address should also be a required field. Select Email. Validating User Entries Scenario When a candidate is entering an application. The company prefers to send all communication through email.
ValidEmailAddress that is shipped as part of the product. When the candidate is entering their personal information. Be sure to save any updates and then create a new case to test changes made to the case type. Save the updated email properties and then Close the Edit Property tab. Click inside the Use Validate field and then use the down-arrow to select ValidEmailAddress from the available validation types. Open the Advanced tab.
Try to enter an invalid email address to ensure that email validation is working. Accessing Data in the Application This lesson group includes the following lessons: Add columns using fields in the following table. This is used in various steps of the candidate process. Describe the Position table using the following information: Position details will include the job details.
This data can be used to populate the newly created data table. Click Add a new Data Table to begin the wizard.
Create a table that will keep track of open positions. Enable the data page creation so that the results of the data table can be accessed in the application.
To enter data. When entering Class Name and Derives From values into auto complete fields. Append —Position to Class Name. Use the autocomplete feature to pick the class name. Enable Create Data Pages and then enter the following: Lookup Data Page: If a new window does not open up. Enter properties from the following table. Leave Key enabled in the first row of properties. Add rows by clicking the List Editor link.
About the Data Table Wizard www. Click the Add a row link and enter values for fields using the spreadsheet referred to in the Approach section of this exercise. Accept defaults which use the current ruleset and ruleset version and then click Generate. Use the data page that is created by the Data Table wizard to display the list of all positions.
The available positions should have an ID stored internally but should display the label to help the candidate to easily select the position. Hints Open the Data Explorer to see the name of the data page that contains the position list. Open the data table landing page to see which property has id and value in the data table. The Position Applied For field must be able to perform a lookup in the list of all positions that are currently open in the company. Click the change link and change the control to Dropdown.
Note that lookup is done by ReqID the position number but the operator will see pyLabel the position title. Save changes to the section and then Close the Edit Section tab. In the List Source section. From the Designer Studio menu. Optional Exercise Open the Data explorer and then expand Open Position Details to view the data pages used to manage open positions.
At the bottom of the page. Dropdown control Properties — General tab www. This screen should display details based on the position the candidate has selected. Approach Configure the ScreenCandidate section to use a new embedded section.
The parameter used for lookup should be the property that the candidate has used for selecting the position. When the recruiter performs the screen candidate step. Create a new section within the Screen Candidate section and add the following fields in a dynamic layout — use Inline Grid Triple or Inline Grid Double as the format. The fields added must be marked as read-only in the edit options fields on the presentation tab. Save the section where you included the new section.
The parameter for data page should use. Open the process outline for the Screen Candidate step in the Qualify stage and then click Open Section for the Screen Candidate action.
Make sure the Use property label field is enabled to see the label. Add a Text Input control to add the field into the cell. The section can be created by entering a name and clicking the icon next to the section field. Open the Layout palette.
Click the new Section link and drag it to be located above the existing layout before releasing the mouse button. Hints The section can be added by using the layout palette. ReqID property and select to Use property default for the display label. In the Cell Properties dialog. In the Section Include dialog. Click the Presentation tab and select Read Only always in the Edit options field.
When the Section rule form appears for PositionDetails. PositionAppliedFor 5. Click the View Properties icon for the new Text Input cell. Click OK to close the Dynamic layout properties dialog. After returning to the Section rule form for Position Details.
To create the new section. In the Dynamic layout properties dialog. In the Section Record rule form. This will provide all properties Department. Click OK to close the Cell Properties dialog. After returning Section rule form for Position Details.
Optional — Consider experimenting with your section. Move cells around to your preferred order. You could also add a separate layout for Job Description that uses the full screen width.
Some things you can try include adding a label. Save the section and then Close the Section details rule form. Icon Key View Properties icon Open icon www. Return to the Section Include dialog and click OK to close the dialog box.
Return to the Screen Candidate Section rule form and Save changes. The parameter used as input to for the data page lookup should be. As a result. Hints Select Refer to a data page for the Data Access field.
Add a new page property to the Schedule Interview section and name it Position. After the position is selected.
If the recruiter determines that the candidate is not a good fit for the selected position. To ensure that your application functions as it should. Position fields should be Read only as they will not be modified. Use the Configure form link to add a Position property with mode type Page. Do not click Save yet. If the Configure form link is not available.
This will open additional fields. When the Data Type details form appears. Changes made in this exercise will enable the auto-populate feature for this property. PositionAppliedFor 3. Click the Open Position Details edit icon. Select a source: The system then moves to Select Target Position where it uses a decision rule to decide if the candidate is a good fit for the position.
For the included section that displays position details. The recruiter screens the candidate and enters their feedback in the Screen Candidate step. This allows values for the position details to be accessed from the data page. From the process outline for the Qualify stage.
In the select different position screen. The decision rule comes up with three choices — the candidate is a good match for the selected position. Add fields for the PositionAppliedFor text mode property and Position page property. When a new position is selected the process should refresh the section that displays all the position details.
Apply the refresh condition so that the section refreshes when the value in the dropdown changes. When the system decides that the candidate is a better fit for a different position. The case moves to a recruiter in the Qualify stage. Open the section and change the control used for PositionAppliedFor to Dropdown.
Configure the event and actions to update the position page fields in the action tab. Select a different position to test these changes. Change the field control to Dropdown. You can force a refresh when the operator is in the included section. Hints In the form configuration.
Make all of the fields read-only. Click Configure form for the Select New Position action. Open the process outline for the Qualify Step by clicking Configure process detail from the Case Designer stages view.
Post Value will submit changes without clicking the submit button. Make the following changes to the PositionAppliedFor cell property. Control List Source: Add a PositionAppliedFor text mode property and a Position page property. ReqID property. Save updates to the case and then click Open Section to open the Select New Position section rule form. Click the view properties icon to view properties for the section that displays position details.
Set the Page context to Use data page. Click Create an action set. View properties for the PositionAppliedFor cell and then select the Actions tab.
Click OK to save updates and then Save changes to the section. Use the Open icon to open the refresh condition builder. View properties for the section that displays position details. Leave the section open to try the optional section reuse exercise.
When you reach the Candidate Qualification screen. Optional Exercise: Reuse a Section Check to see if you have a section. Continue submitting forms until you reach the Select New Position screen. If so. Click OK to close the Layout Properties dialog. Change selected position to see changes to this section. Create a new Candidate case process. Set a refresh to occur when the PositionAppliedFor changes. Save changes to the section and case type. And then click Save Changes.
Return to the Schedule Interview Section if the tab is not currently available. When all fields are entered. Drag the existing Position Details section below the Schedule Interview section. View properties for the dynamic layout and change the Layout format from Default to Inline grid double.
Since the section we just included is not. You will probably have the position details included in the Schedule Interview section twice in two different formats.
Right-click the wireframe around the section and select Cut from the menu. After you test the case. If you have duplicate fields. View properties for each field. Save changes to the Schedule Interview section and close the tab. Save changes made to the case type and test your changes before continuing. Save changes to the Schedule Interview section and then test the new included section by running the process and creating a case.
Add the fields returned from the data transform to the Background Check step. View the data transform that is imported to see what fields are returned when a background check is performed. For this training. We also need to add a flow name and fields to the Background Check step. To perform the background check. This task has been performed before. Once properties that will contain the return values from the background check have been added to the flow.
Fields that will be added to the flow are those returned from the background check transform that is imported. Download to your local system and unpack the zip archive. If the file is missing from the next step. Browse to this file. The download will contain both instructions and the import file: Procedure This procedure will consist of five parts: Import rules to perform a background check.
Leave this cell blank and click Next to continue. Select the file to import and then click Next. To view components that will be imported. Scroll through the list of available files and select the Background Check file to import. Follow the steps below to add SSN to the Candidate data object type: The first thing we need to do is to add SSN to the Candidate properties. Click Next and then view results. Click Done to close this window. A data transform will return information on any previous bankruptcy.
View components. Leave the default property type Text and click Save. Select the SSN property and drag it into the Candidate section. View properties for the Social Security Number cell and make it a Required field. Open the process outline for the Decision Stage and select the Background Check step. View the BackgroundSimulation Data Transform to see what fields it returns. CreditReport and CriminalRecord pages. Return Back to stages. Look for the Bankruptcy.
Part 4 — Add Fields to the Background Check step 1. Open the Background Check step of the Decision stage in the process outline. You should change them all to Read Only. Looking back at the BackgroundSimulation Data Transform viewed earlier in this exercise. These will be: After each page property is added. You may have to return back to stages and then re-open the process outline.
Click Save to close the Form Configuration rule form. Open the Layout menu and then drag a new Section above the default section that was created when fields were added to this step. To obtain the correct values to define the data page: Note that it may not be available using a down-arrow in the autocomplete fields.
Set the page context of the section to Use data page. In the Application Explorer.
Scroll down below this BackgroundCheck UI Section to the sections that were created automatically when fields were added. Save the section and then Close the section rule form tab. Select each of these sections. Always save updates to the case type and test the case before continuing.
To active the new background check data transform. Do this for each of the three sections that were replaced when the BackgroundCheck section was imported. Automating Business Policies This lesson group includes the following lessons: For average calculation. This is automatically calculated as a two-step process. Two properties. Technical Skill Rating and Interviewer Rating add all three ratings and divide by 3. Use Candidate. Position and Offered Salary as fields to display.
Mark all of them except OfferedSalary as read-only. Assessment Rating is calculated as the average of Interpersonal Skill Rating. Part 2 — Create the flow action and section for Extend Offer the screen. Use the following login information Role: Assessment Rating and Offered Salary. Hints To create the necessary properties. Click the gear icon next to the calculated field to define the declare expression rule. In the Action field for the Determine Compensation flow.
To begin adding fields. This will open a calculation dialog. Set the value as specified in the scenario and save the rule. In Form Configuration. Ensure there is a name in the Action field and then click Configure form to open Form Configuration. Click on the Configure process detail link under the Offer stage.
Click the gear icon next to the first calculated field to define the declare expression rule. Make both fields decimal and specify that they will be calculated. When you return to Form Configuration. In the calculation dialog. Add Assessment Rating and OfferedSalary fields. Set the value of Assessment Rating to be equal to the Value of. AssessmentRating and then click OK. Save your Form Configuration and then save changes to the case type. It can be edited to add more existing fields from the App Explorer work class.
Open the flow action rule just created by clicking the Open icon next to the Action name. Save any changes to the case and run the process to test a case instance. When the Edit Flow Action rule form displays. The Determine Compensation section rule will display. Create a new case to test the flow and check the value of the offered salary in the Determine Compensation user interface.
Follow the steps below: Open the process outline view for the Offer stage and select the Extend Offer step. Part 2 Create the flow action and section for Extend Offer screen. Mark all fields as Read Only. Add fields for Candidate Full Name.
Open the AssessmentRating expression and view the rule form. View the two new declare expressions using the steps below. Optional Exercise After a declare expression is added to the case. Skip Screening Process Scenario If the candidate to be interviewed is referred by an employee. Specify to Skip the stage when the candidate is referred by an employee by entering IsReferredByEmployee.
Open the Stage Configuration form for the Qualify stage. Create the When rule by clicking on the magnifying glass after naming it. Hints Skip Stage When can be configured configuring stage behaviors for the Qualify stage. Click the Open icon next to the When rule name to open the form used to create the When rule. The Qualify stage should be skipped when the referred by employee property is set to true. Test the When rule by creating a new Candidate case.
Configure the When rule to check for the ReferredByEmployee property to be equal to true and then click Create and close. Hints Use the Configure form link to add fields to the step Run the process to create a new case and then use the UI inspector to open the new section.
While it is not required we recommend that you try to complete this exercise as it will help to reinforce the concepts taught in this course. Scenario If the candidate is applying for a position in the Engineering Department the company would like to provide an option for the candidates to include a sample of their code.
Department field to see if the position is in the Engineering department. The When rule can compare the. Do not select Referred by Employee. Open the process outline for the Qualify stage. Select the Request Technical Sample step from the stage steps and then click Configure form.
Add the fields listed in the table below. Stop when you read the Request Technical Sample step. Use the Run or Create buttons to create a new Candidate case. Click OK to close the cell properties form. Save the new When condition. Give the When condition record the short description name Engineering Position and then click Create and open. Set the value to Engineering and then click OK. To select the Department. Append a period and then use the down arrow again to select Department. Change the control to Rich text editor.
Click the Open icon to the right of the empty … and when cell. In the Edit When rule form. Save the section changes and then Close the Edit Section tab.
Note that due to the order of the steps in this stage. Click OK to close the Step Configuration dialog. Save updates to the case type and Run the process to create a case so you can test the changes made in this exercise. The condition should now be available when you click in the …and when cell and use the downarrow to view a list of When conditions in the Step Configuration dialog. To test a decision shape. PRPC evaluates a decision table by starting with the top row and working down to the bottom row.
To use a decision table to direct flow processing. Once they complete the telephone call. Hints In order to use the Property Screener Feedback — which is defined for the Candidate case — you must create the decision in the same class as the property. If your decision table does not return the expected result.
This table should evaluate the value of the Screener Feedback property. The VP of HR has requested that the case be directed through the process automatically.
Create a decision table to direct the Candidate case through the Determine Target Position process. In the Screener Feedback property form. When you associate the decision table with the Is Candidate Qualified? View Properties for the Is Candidate Qualified?
From the Determine Target Position step in the process outline for the Qualify stage. Click the Open icon to the right of the Rule field on the Decision Properties rule form to create the decision table. Open the Qualify stage in the process outline. Open the Screener Feedback property in one of the following ways: Create a Candidate case. Matches the position Matches a different position Does not match any position Save the updated Screener Feedback rule form.
Click the Insert row after icon to add an else if row to the table. In the Label field. Enter Selected Position in the Result column. In the if row. The entry in the Applies To field is a class reference. For now. In this row. Click the column header under Conditions and select the Screener Feedback property.
In the otherwise row. Click Save to return to the decision table form. In the. Unit test the decision table by selecting Run from the Actions menu. Save and then close the Decision Table rule form. Part 2 — Check Decision Shape Connectors Follow the steps below to ensure that the connectors leaving your decision shape match the return values in the decision table. Save the decision table. Open the Determine Target Position step in the process outline. ScreenerFeedback field.
Ensure that the connectors from the "Is Candidate Qualified" decision shape match the return values in this table. Save changes to the process diagram. Right-click and select View Properties for each of the connectors that exit the decision shape. Select the Matches a different position option. You may be directed to the Request Technical Sample assignment before a new position is selected. Consider changing the order of your steps so that the technical sample is requested after the final target position is determined.
Verify that the case is directed to the Select New Position assignment. Ensure that the result matches one of the results in the decision table.
About Decision Tables. Create a new case. Hints To create a decision tree from the decision shape. Approach Create the Candidate Scoring decision tree to evaluate the interview for each candidate. The VP of HR would like to automatically reject candidates who scored too low on the interview.
The Assessment Rating is greater than. This exercise should be performed using the Internet Explorer IE browser. The overall Assessment Rating is greater than. The Assessment Rating is. If you have trouble getting the tools to work. View Properties for the Candidate meets standards decision shape. PRPC evaluates decision trees by starting with the top condition and working down to the otherwise condition at the bottom.
Open the AssessCandidate flow. If your decision tree does not return the expected result. Click [result] and enter No in the resulting field. Click return and select continue to create a subcondition. When the Decision Properties dialog appears. Click the Insert After icon to create a new row below the one you just completed. Give the rule the Label name Candidate Scoring and then click Create and open. In the left field type a period. In the right field.
Create three subconditions to test if either the Interviewer Rating is less than or equal to. In the new row. For each condition.
Close the test window. Save changes to the case type and then test by running the process to create a case. From the Actions menu of the Decision Tree rule form. If a result value is not set. In the dialog. Click OK to close the Decision Properties dialog. Click Run Again. About Decision Trees www. Ensure that the result connectors in the Assess Candidate flow match the return values in the decision tree. Right-click and View Properties for each of the connectors leaving the decision shape.
Save the decision tree rule and then Close the Decision Tree rule form. Advanced Case Processing This lesson group includes the following lessons: The Qualify Stage starts the screening process. Routing to get Approval for Offer Scenario After the candidate information is collected. Hints Click on the stage name and then click configure process detail to open outline view. The company has many recruiters and the case must be routed appropriately so that any of them are able to select and work on it.
Click the step name to access the assignment where we can change routing information to route the case to a Workbasket. The assignment must be routed to a group-wide workbasket. Creation of a more task-specific workbasket is typically the responsibility of a Senior System Architect.
To test the change. Procedure Follow the steps below to update the routing field: Open the Screen Candidate step in the process outline of the Qualify stage. In the Routing frame: Route to: It should be assigned to the default SAE workbasket.
Click the Conduct telephone interview Qualify link to continue processing. Select the default SAE workbasket. Configure your solution to make sure both Wrap-up and Post-Rejection stages are resolution stages. Create a new alternate stage named Post-Rejection. Hover over the Wrap Up stage until the down-arrow appears. They would like an easier way to determine where the case gets resolved.
Click to open the drop-down menu and select Configure stage behaviors to open the Stage Configuration dialog. The alternate stages can be added by using configure alternate stages in the actions menu. Identifying the Resolution Stages Scenario The business users have reviewed the stage based case design approach. Hints Stage behavior can be configured by clicking on the arrow which appears when hovering over the stage name. Enable the Is this a resolution stage? Click the Alternate stage name and rename to Post Rejection.
If you already have a Post Rejection alternate stage. Using instructions in the previous section configure stage behaviors to make Post Rejection a resolution stage. View properties for the End shape in the process diagram. Save updates to the flow image and then Close the Resolve-Reject process diagram tab. In the End Properties dialog. Hover over the step name.
Rename the default step in the Post Rejection stage to Resolve-Reject. Save updates to the case type. Click OK to close the End Properties dialog.