Looking for:
Pega prpc video tutorial free download |
.
Good Luck for your job trials.. Your email address will not be published. Blog Instructor Led Live Training. We are uploading more videos soon. Next tutorial Robotic Process Automation. Lesson Introduction to Pega. Pega Systems Inc. Free Material 1 Course Attachment Download.
Quiz Pega is the software for customer centrality. A data table is a simple structure consisting of the rows of a Pega 7 Platform concrete class that includes only scalar Single Value properties. Informally, a data table is the Pega 7 Platform's internal representation of a "flat file" that contains no repeating groups.
Lesson How we can create a pega sample application? So you have the Pega 7 platform up and working. Now what? This structure includes more than just an application name. It also describes certain business and technical perspectives. To catch these aspects Pega comes with a wizard called App Express. This wizard will effectively create rules to define the Organizational and Class Hierarchies. The Document Application tool captures information and images from any application in your stack and generates the customizable application, application outline and specification documents that you can share with stakeholders.
This tool was previously called the Application Document wizard. Lesson How can we create an Agent? An agent schedule instance Data-Agent-Queue class determines whether an agent runs and for a multinode system on which server nodes it runs. Agent schedules cannot be created manually. The Agent Manager master agent generates agent schedule instances from agents rules Rule-Agent-Queue rule type. The Agent Manager on your Pega 7 Platform system generates at least one agent schedule instance for each agent rule.
In a multinode system, for each agents rule, the Agent Manager generates one agent schedule instance for each node. For example, if a clustered Pega 7 Platform system has five nodes, then there are five Pega-ProCom agent schedule instances generated from the Pega-ProCom agents rule. Lesson How we can create a Pega Report? Both managers and developers can create and manage reports by using the portal that is best suited for their roles.
For more information about how to create reports, see the following Help topics: Creating reports in Designer Studio, Creating reports in Pega Express, Creating reports in Case Manager. Lesson How can we create a pega Integrator? An Integrator shape identifies an activity that connects your Pega 7 Platform system to an outer system to send or receive data.
An integrator shape can connect to a customer master database to retrieve account balances or verify account numbers and status. Integrator shapes use activities with Connect as the Activity Type that call connector rules Rule-Connect- rule types.
Practice: Quiz: Variables Quiz: Variables. Chaitanya I want to learn pega. Deepak Thank you for the feedback. Deepak Good Luck for your job trials.. Debasish Dash nice tutorial. Deepak Thanks for your kind words Debasish, appreciate it. Submit A Comment Your email address will not be published.
Asha24 Believes in Skill Up. Scale Up.. Your email address.
Pega prpc video tutorial free download.Document Information
A data table is a simple structure consisting of the rows of a Pega 7 Platform concrete class that includes only scalar Single Value properties. Informally, a data table is the Pega 7 Platform's internal representation of a "flat file" that contains no repeating groups.
Lesson How we can create a pega sample application? So you have the Pega 7 platform up and working. Now what? This structure includes more than just an application name. It also describes certain business and technical perspectives. To catch these aspects Pega comes with a wizard called App Express. This wizard will effectively create rules to define the Organizational and Class Hierarchies.
The Document Application tool captures information and images from any application in your stack and generates the customizable application, application outline and specification documents that you can share with stakeholders.
This tool was previously called the Application Document wizard. Lesson How can we create an Agent? An agent schedule instance Data-Agent-Queue class determines whether an agent runs and for a multinode system on which server nodes it runs.
Agent schedules cannot be created manually. The Agent Manager master agent generates agent schedule instances from agents rules Rule-Agent-Queue rule type.
The Agent Manager on your Pega 7 Platform system generates at least one agent schedule instance for each agent rule. In a multinode system, for each agents rule, the Agent Manager generates one agent schedule instance for each node. For example, if a clustered Pega 7 Platform system has five nodes, then there are five Pega-ProCom agent schedule instances generated from the Pega-ProCom agents rule. Lesson How we can create a Pega Report? Both managers and developers can create and manage reports by using the portal that is best suited for their roles.
For more information about how to create reports, see the following Help topics: Creating reports in Designer Studio, Creating reports in Pega Express, Creating reports in Case Manager.
Lesson How can we create a pega Integrator? 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.
From the Properties panel Select the step and then click the Configure form link. 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 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. Important: 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. Note: 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.
Exercise: 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.
Use property defaults, including a property type of Text. Save and then Close the property rule form for the new Skills property. 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. Select the Professional Info step in the stage steps. When the section opens, it contains only a Grid Repeat Layout. Since Skills is not a list object, we need to add a new layout that can hold this property.
Select Layout from the Layout menu. Click OK to close the layout cell properties form and then Save changes to the section. Close the Section tab. To allow more space in the screener comments, do the following: Open the Qualify Stage in the process outline.
Select the Screen Candidate step and then click Open section. Using the instruction beginning in step 13, view properties for the Screener Comments cell and set the field to use a Text Area control. Exercise: Adding List-Based Controls Scenario In an effort to reduce data entry errors for candidate cases, the HR department would like to limit the list of values for the Screener Feedback field to: Fits the Role Requires Additional Training Is Not a Fit for the Role Similarly, for the relevant experience field, they want the recruiter to only be able to select yes or no.
Approach In the Screen Candidate step of the Qualify stage, modify the control for the Screener Feedback field to use a dropdown menu with the following selections: Fits the Role Requires Additional Training Is Not a Fit for the Role For relevant experience, use a radio button to show the values instead of the checkbox. Hints To edit cell or section properties using the UI Inspector, Run the process to create a new case and then do the following: While the applicable form is displayed, click the UI Inspector icon.
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. The list of values is stored as local list in the property definition.
The dropdown exists in the basic palette. The radio button also exists in the basic palette. Procedure Follow the steps below: Create a new Candidate case using either the Run button or the Create menu. Submit user input for each process step until you reach the Screen Candidate step. Hover over the Screener Feedback field until the Information Panel displays and then click the blue ScreenerFeedback property link for the Cell.
Save changes and then return to the open case. 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.
Click OK to close the layout cell properties dialog. After returning to the Screen Candidate layout section form, click inside the Relevant Experience cell then click the View Properties icon to view Relevant Experience layout cell properties. Click the change link in the layout cell properties form and then select Radio buttons from the basic input group. Save the Screen Candidate section changes and then Close the tab. Save updates to the Candidate case type. Refresh the open case or create a new case to test changes made to the Screen Candidate user interface.
Exercise: Identifying Mandatory Fields Scenario When a candidate is entering an application, the company wants to ensure that something is entered for each of the following fields: Last Name Email Address Previous Job Details o.
Approach Use the Stage Designer view to make sure the fields are marked as required. If you have already made changes in the section rule, the section cannot be opened in the stage designer view. In that case, open the section rule and mark the field as required.
To make Email a required field, click the Personal Info step in the stage steps area to view the properties panel for Personal Info. Click Open Section. Note: If you have opened and saved a section the Configure form link may no longer be visible. Email address should also be a required field. Save changes to the section and then Close the section tab. Be sure to save any updates made to sections and then to the Candidate case type.
Create a new case to test changes made to the case type. Exercise: Validating User Entries Scenario When a candidate is entering an application, the company might want to contact them during case processing to notify them of their hiring decision.
The company prefers to send all communication through email. When the candidate is entering their personal information, we need to make sure they are entering a proper email address. Approach Use the standard edit validate rule, ValidEmailAddress that is shipped as part of the product. Select Email. Open the Advanced tab. Click inside the Use Validate field and then use the down-arrow to select ValidEmailAddress from the available validation types.
Be sure to save any updates and then create a new case to test changes made to the case type. Try to enter an invalid email address to ensure that email validation is working. Exercise: Create a New Data Table Scenario In the candidate application process, candidates need to select the position they are applying for.
The SAE HR team gets approvals for open positions and, once the approval is received, they create the position. Position details will include the job details, experience required, salary information, hiring manager and recruiter information.
This is used in various steps of the candidate process. Approach Use the Data Table wizard, available from the Designer Studio Data Model menu, to create a data table that will contain open positions.
Add columns using fields in the following table. Download the Excel spreadsheet DataTables. This data can be used to populate the newly created data table. Click Add a new Data Table to begin the wizard. Use the autocomplete feature to pick the class name.
Enable the data page creation so that the results of the data table can be accessed in the application. To enter data, click the icon to edit instances and then add each row one at a time. Note: If a new window does not open up, try changing to a different browser. Create a table that will keep track of open positions, using the following information.
Class Name Description Derives From. Append Position to Class Name. Leave Key enabled in the first row of properties. Enter properties from the following table. Accept defaults which use the current ruleset and ruleset version and then click Generate.
Add rows by clicking the List Editor link. Approach section of this exercise. Note that you can add additional rows later using the Edit data instances. Exercise: Populate Dropdown From a Data Page Scenario When the candidate is entering personal information, they should also select the position they are applying for. 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.
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. Click the View properties icon.
In the List Source section, enter values from the following table. Note that lookup is done by ReqID the position number but the operator will see pyLabel the position title.
Type Data page Property for value Property for display text. 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, test the connection to the database table. When the recruiter performs the screen candidate step, they should see details of the position for which the candidate is applying.
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.
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. Hints The section can be added by using the layout palette.
The parameter for data page should use. The section can be created by entering a name and clicking the icon next to the section field. Add a Text Input control to add the field into the cell. Make sure the Use property label field is enabled to see the label.
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.
Procedure Follow the steps below: Open the process outline for the Screen Candidate step in the Qualify stage and then click Open Section for the Screen Candidate action. Open the Layout palette.
Click the new Section link and drag it to be located above the existing layout before releasing the mouse button. In the Section Include dialog, use information from the following table to indicate that the section will be populated by a data page and that the parameter used for lookup will come from the PositionAppliedFor field. Dynamic Layout. In the Dynamic layout properties dialog, select Inline grid triple from the Layout format dropdown menu.
Click OK to close the Dynamic layout properties dialog. After returning to the Section rule form for Position Details, open the Basic pallet, click and hold Text Input and drag it into the new section.
Click the View Properties icon for the new Text Input cell. In the Cell Properties dialog, configure the Text Input control to use the. ReqID property and select to Use property default for the display label. Click OK to close the Cell Properties dialog. After returning Section rule form for Position Details, repeat steps 8 through 10 above add a new text input cell and update properties for the remaining fields in the table shown in the Approach section for this exercise.
Note: In the Cell Properties dialog, use the down-arrow to select from available properties. This will provide all properties Department, MinSalary, etc. Optional Consider experimenting with your section.
Some things you can try include adding a label, such as Position Title to. You could also add a separate layout for Job Description that uses the full screen width. If the recruiter determines that the candidate is not a good fit for the selected position, he or she can select a different position. After the position is selected, we need to update the position details to correctly determine the appropriate offered salary.
Approach Perform the tasks listed below. Add a new page property to the Schedule Interview section and name it Position. Note: Normally, a Senior System Architect would be responsible for configuring a page to automatically populate values for the properties it contains. As a result, this feature is not taught in this course.
However, not automatically populating these property values causes other parts of our application specifically, the calculation for the salary offered to a candidate to function incorrectly. To ensure that your application functions as it should, we have included this exercise. The parameter used as input to for the data page lookup should be.
Use the Configure form link to add a Position property with mode type Page. Notes: If the Configure form link is not available, add the Position page manually, using the App Explorer, as detailed in an earlier exercise. Position fields should be Read only as they will not be modified. Do not click Save yet. Automatically source data at runtime.
This will open additional fields. Changes made in this exercise will enable the auto-populate feature for this property. The case moves to a recruiter in the Qualify stage.
The recruiter screens the candidate and enters their feedback in the Screen Candidate step. 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.
The decision rule comes up with three choices the candidate is a good match for the selected position, the candidate should be matched with a different position, or the candidate should be rejected. When the system decides that the candidate is a better fit for a different position, it displays a screen for the recruiter to see the position the candidate has currently applied for, and allows the recruiter to switch to a different position.
In the select different position screen, the candidate should see a dropdown field containing the list of available positions and a section that displays all the data elements for a position. When a new position is selected the process should refresh the section that displays all the position details. Approach Configure your solution to modify the Select Position screen to perform the functionality described in the scenario.
Add fields for the PositionAppliedFor text mode property and Position page property. Open the section and change the control used for PositionAppliedFor to Dropdown. For the included section that displays position details, switch the page context to use a data page instead of the embedded page. This allows values for the position details to be accessed from the data page. Apply the refresh condition so that the section refreshes when the value in the dropdown changes.
Hints In the form configuration, enter Position to display the currently selected position data page so that the operator can view all the properties on the position page.
Make all of the fields read-only. Change the field control to Dropdown. Configure the event and actions to update the position page fields in the action tab. Post Value will submit changes without clicking the submit button. You can force a refresh when the operator is in the included section, or add it as another action for the dropdown control.
Select a different position to test these changes. Procedure Follow the steps below: Open the process outline for the Qualify Step by clicking Configure process detail from the Case Designer stages view. Click Configure form for the Select New Position action. Add a PositionAppliedFor text mode property and a Position page property. All fields in the Position data page should be Read Only. Click Save to close the Form Configuration dialog. Save updates to the case and then click Open Section to open the Select New Position section rule form.
Use the View properties icon. Reminder: Enter dot. ReqID property. Click the view properties icon to view properties for the section that displays position details. Click OK to save updates and then Save changes to the section. View properties for the PositionAppliedFor cell and then select the Actions tab. Click Create an action set. On the Actions tab of the Cell Properties rule form for the PositionAppliedfor Field, create a new action set to occur on a Change event and Post value as the action.
View properties for the section that displays position details. Use the Open icon to open the refresh condition builder. Click OK to close the Layout Properties dialog. Optionally, move fields around or change the dynamic layout properties to an inline grid double layout format.
Leave the section open to try the optional section reuse exercise. Save changes to the section and case type. Create a new Candidate case process. When you reach the Candidate Qualification screen, select Different Position. Continue submitting forms until you reach the Select New Position screen. Change selected position to see changes to this section.
Optional Exercise: Reuse a Section Check to see if you have a section, created in an earlier exercise, which contains fields from the Position page.
If so, add it below the current Schedule Interview section using the following steps. Return to the Schedule Interview Section if the tab is not currently available, open the section from the process outline for the Schedule Interview step in the Interview stage.
Since the section we just included is not, when you get prompted for the page that the properties in this section are associated with, enter or select the SAE-HRServices-Data-Position class. When all fields are entered, View properties for the dynamic layout and change the Layout format from Default to Inline grid double. View properties for each field, select the Presentation tab of the Cell Properties dialog and change the Edit options to Read only.
Save changes to the Schedule Interview section and then test the new included section by running the process and creating a case. Note: You will probably have the position details included in the Schedule Interview section twice in two different formats. After you test the case, you can decide to remove one of the duplicate sections.
If you have duplicate fields, return to the Schedule Interview section to remove the section you do not need. Right-click the wireframe around the section and select Cut from the menu.
Exercise: Reusing Data Transform for Background Check Scenario As part of the decision process, the company wants to conduct a background check on the candidate. This task has been performed before, by other applications, and the objects required to perform the process already exist.
To perform the background check, we will implement an existing data transform and User Interface section. Normally, you would import a file that contains rules that you want to use in your application. For this training, the file has already been included in your exercise environment, and will appear in the list of files available for import. We also need to add a flow name and fields to the Background Check step.
Fields that will be added to the flow are those returned from the background check transform that is imported. Once properties that will contain the return values from the background check have been added to the flow, we can reuse the User Interface Section that was included in the import. View the data transform that is imported to see what fields are returned when a background check is performed. Add the fields returned from the data transform to the Background Check step, and then display them using the User Interface section that was imported.
Procedure This procedure will consist of five parts: Import rules to perform a background check. Select the file to import and then click Next.
Note: Leave this cell blank and click Next to continue. If the file is missing from the next step, return back to this step. Download to your local system and unpack the zip archive. Browse to this file. Scroll through the list of available files and select the Background Check file to import. To view components that will be imported, select Enable advanced mode to provide more granular control and then click Next.
A data transform will return information on any previous bankruptcy, a recent credit report and criminal record. The first thing we need to do is to add SSN to the Candidate properties. Follow the steps below to add SSN to the Candidate data object type:.
Part 4 Add Fields to the Background Check step 1. View the BackgroundSimulation Data Transform to see what fields it returns. Open the Background Check step of the Decision stage in the process outline. If the action hasnt already been added, name it Perform Background Check and then click the Configure form link. Looking back at the BackgroundSimulation Data Transform viewed earlier in this exercise; add the fields that were returned by the data transform. You should change them all to Read Only.
Click Save to close the Form Configuration rule form, click Save to save changes to the case type and then click Back to stages. Part 5 Edit the Background Check Section to use the imported section From the process outline for the Background Check step in the Decision stage, click Open Section to view the default section that was created when fields were added.
Note: You may have to return back to stages and then re-open the process outline. Open the Layout menu and then drag a new Section above the default section that was created when fields were added to this step. Set the page context of the section to Use data page.
Note that it may not be available using a down-arrow in the autocomplete fields, so be sure to spell correctly. The SSN will be used to perform the background check Find it by first typing a dot. Append another dot. Scroll down below this BackgroundCheck UI Section to the sections that were created automatically when fields were added. Select each of these sections, right-click and select Delete from the menu. Do this for each of the three sections that were replaced when the BackgroundCheck section was imported.
Reminder: Always save updates to the case type and test the case before continuing. To active the new background check data transform, enter as the new candidates SSN. Exercise: Determine Offered Salary Scenario In the Determine Compensation step of the Offer stage, the system must show the salary that will be offered to the candidate.
This is automatically calculated as a two-step process. Two properties, Assessment Rating and Offered Salary, must be created. Approach Part 1 Configure your solution to use two Declare Expressions. For average calculation, use the average function or compute the sum of all three factors and divide by three.
Part 2 Create the flow action and section for Extend Offer the screen. Use Candidate, Position and Offered Salary as fields to display. Mark all of them except OfferedSalary as read-only.
Hints To create the necessary properties, declare expression rules, section and flow action rules, click the Configure Process Details link under the associated stage name. In the Action field for the Determine Compensation flow, ensure there is an action name. To begin adding fields, click Configure form. In Form Configuration, make the fields decimal and select Calculated read only to create new properties. Click on the Configure process detail link under the Offer stage.
Ensure there is a name in the Action field and then click Configure form to open Form Configuration. Add Assessment Rating and OfferedSalary fields. Make both fields decimal and specify that they will be calculated. Click the gear icon next to the first calculated field to define the declare expression rule.
This will open a calculation dialog. Set the value of Assessment Rating to be equal to the Value of. When you return to Form Configuration, click the gear icon next to the second calculated field, In the calculation dialog, set the value of Offered Salary to. AssessmentRating and then click OK. When the Edit Flow Action rule form displays, open the section created for this flow action by clicking the Open icon for the section. The Determine Compensation section rule will display.
It can be edited to add more existing fields from the App Explorer work class, if needed. Create a new case to test the flow and check the value of the offered salary in the Determine Compensation user interface. Save any changes to the case and run the process to test a case instance. Part 2 Create the flow action and section for Extend Offer screen. Follow the steps below: Open the process outline view for the Offer stage and select the Extend Offer step.
Mark all fields as Read Only. Optional Exercise After a declare expression is added to the case, the declare expression rule can be found in the Application Explorer work class. View the two new declare expressions using the steps below. Exercise: Skip Screening Process Scenario If the candidate to be interviewed is referred by an employee, the HR department wants to change the process by skipping the initial qualification process and schedule the interview directly.
Hints Skip Stage When can be configured configuring stage behaviors for the Qualify stage. Create the When rule by clicking on the magnifying glass after naming it. Specify to Skip the stage when the candidate is referred by an employee by entering IsReferredByEmployee.
Configure the When rule to check for the ReferredByEmployee property to be equal to true and then click Create and close. Test the When rule by creating a new Candidate case. The Qualify stage should be skipped when the referred by employee property is set to true. 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. 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. The When rule can compare the.
Department field to see if the position is in the Engineering department. Select the Request Technical Sample step from the stage steps and then click Configure form. Add the fields listed in the table below.
URL Sample Code. Click Save to close the Form Configuration screen and then Save updates to the case type. Use the Run or Create buttons to create a new Candidate case. Do not select Referred by Employee, so that you will not skip the Qualify stage. Stop when you read the Request Technical Sample step. Change the control to Rich text editor. Click the Open icon. Give the When condition record the short description name Engineering Position and then click Create and open. In the Edit When rule form, double-click to add the condition.
To select the Department, enter a period. Append a period and then use the down arrow again to select Department.
Set the value to Engineering and then click OK. 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. 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. Note that due to the order of the steps in this stage, if the candidate does not match the original Engineering position applied for, a technical sample may still be requested before a new position is selected.
Exercise: Direct Flow Processing with a Decision Table Scenario During the Qualify stage, the recruiter screens the candidate over the telephone to determine if the candidate has accurately portrayed themselves with their resume and the information they provide in the Collect Information stage.
Once they complete the telephone call, the recruiter must assess the candidate and determine whether their qualifications match the targeted position, match a different position, or do not match any currently open position. The VP of HR has requested that the case be directed through the process automatically, based upon the recruiters assessment.
Approach Update the allowed values for the Screener Feedback property to Matches the position, Matches a different position, and Does not match any position.
Create a decision table to direct the Candidate case through the Determine Target Position process. This table should evaluate the value of the Screener Feedback property, and direct the case according to the following logic: If the recruiter selects Matches the position, return the result Selected Position. If the recruiter selects Matches a different position, return the result Different Position. If the recruiter selects Does not match any position, return the result Reject.
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.
To use a decision table to direct flow processing, the decision table results must correspond to the connectors on the corresponding decision shape.
To test a decision shape, select Run from the Actions menu and enter the condition you wish to test. PRPC evaluates a decision table by starting with the top row and working down to the bottom row, until it returns a true result. If your decision table does not return the expected result, click Show Conflicts to identify any rows that are not being evaluated. If necessary, re-order the rows to ensure that PRPC tests each row. When you associate the decision table with the Is Candidate Qualified?
Open the Qualify stage in the process outline. Open the Screener Feedback property in one of the following ways: Create a Candidate case, run the process until you reach the Screen Candidate step and then use the UI Inspector to open the ScreenerFeedback property. In the Screener Feedback property form, expand Display and Validation and replace the validation table values with the following values.
Matches the position Matches a different position Does not match any position Save the updated Screener Feedback rule form. Click the Open icon to the right of the Rule field on the Decision Properties rule form to create the decision table. In the Label field, enter Is the candidate qualified for the position?
Note: The entry in the Applies To field is a class reference, and represents the Candidate case. For now, verify that the class reference in the field ends with -Work-Candidate. Click the column header under Conditions and select the Screener Feedback property. Click Save to return to the decision table form. In the if row, click in the Screener Feedback column and use the down-arrow to select Matches the position. Enter Selected Position in the Result column.
Click the Insert row after icon to add an else if row to the table. In this row, select Matches a different position as the condition, and enter Different Position as the result. In the otherwise row, enter Reject as the result. Note: Ensure that the connectors from the "Is Candidate Qualified" decision shape match the return values in this table. Save the decision table. Dont close the Edit Decision Table tab.
Unit test the decision table by selecting Run from the Actions menu. In the. ScreenerFeedback field, enter each of the allowed choices Matches the position, Matches a different position, and Does not match any position and then click Run Again to verify that the table returns the correct result. 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.
Open the Determine Target Position step in the process outline. Right-click and select View Properties for each of the connectors that exit the decision shape. Ensure that the result matches one of the results in the decision table. Save changes to the process diagram. Create a new case, and advance to the Screen Candidate step. Select the Matches a different position option.
Verify that the case is directed to the Select New Position assignment. Note: 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. Exercise: Direct Flow Processing with a Decision Tree Scenario As part of the process of assessing a candidate, the feedback provided by the interviewer is reviewed and used to decide whether or not to hire the candidate for the position.
The VP of HR would like to automatically reject candidates who scored too low on the interview. If you have trouble getting the tools to work, ensure you are using IE for this exercise. Approach Create the Candidate Scoring decision tree to evaluate the interview for each candidate, and automatically return No for a candidate who meets any of the following criteria: The Assessment Rating is. The Assessment Rating is greater than.
The overall Assessment Rating is greater than. Hints To create a decision tree from the decision shape, first set the Type on the properties panel to Decision Tree.
PRPC evaluates decision trees by starting with the top condition and working down to the otherwise condition at the bottom, until it returns a true result. If your decision tree does not return the expected result, click Show Conflicts to identify any conditions that may not be evaluated.
Expand Candidate Process Flow to see the flows used by the Candidate case type. Open the AssessCandidate flow. View Properties for the Candidate meets standards decision shape. 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, enter. Click [result] and enter No in the resulting field. Click return and select continue to create a subcondition.
Create three subconditions to test if either the Interviewer Rating is less than or equal to. For each condition, return No. In the otherwise row, click [return] and enter Yes in the resulting field. From the Actions menu of the Decision Tree rule form, select Run to test the decision tree. In the dialog, enter a value for the first property field on the form. Click Run Again, and enter property values in each new field until the decision tree returns a result.
Close the test window, Save the decision tree rule and then Close the Decision Tree rule form. Click OK to close the Decision Properties dialog.
Right-click and View Properties for each of the connectors leaving the decision shape. If a result value is not set, use the down arrow to select Yes or No. Note: Ensure that the result connectors in the Assess Candidate flow match the return values in the decision tree. Save changes to the case type and then test by running the process to create a case. Exercise: Routing to get Approval for Offer Scenario After the candidate information is collected, the case moves to qualify stage.
The Qualify Stage starts the screening process, which must be assigned to a recruiter. 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. Approach Configure your solution to add routing to the Screen candidate step of the Qualify stage. 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. Hints Click on the stage name and then click configure process detail to open outline view.
Click the step name to access the assignment where we can change routing information to route the case to a Workbasket. 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: Workbasket. Select the default SAE workbasket. To test the change, create a new Candidate case and advance it to the Qualify stage. It should be assigned to the default SAE workbasket.
Exercise: Identifying the Resolution Stages Scenario The business users have reviewed the stage based case design approach. They would like an easier way to determine where the case gets resolved. Approach Perform the following tasks: Create a new alternate stage named Post-Rejection. Configure your solution to make sure both Wrap-up and Post-Rejection stages are resolution stages.
Add a step in Post-Rejection stage and set the work status as Resolved-Rejected. Hints Stage behavior can be configured by clicking on the arrow which appears when hovering over the stage name. The alternate stages can be added by using configure alternate stages in the actions menu.
Hover over the Wrap Up stage until the down-arrow appears. Click to open the drop-down menu and select Configure stage behaviors to open the Stage Configuration dialog. If you already have a Post Rejection alternate stage, skip to step 5. If you dont have a Post Rejection alternate stage, open the Actions menu in the Designer Studio toolbar and select Configure Alternate stages.
Click the Alternate stage name and rename to Post Rejection. Using instructions in the previous section configure stage behaviors to make Post Rejection a resolution stage. Rename the default step in the Post Rejection stage to Resolve-Reject. Hover over the step name, open the drop-down menu and select Open. View properties for the End shape in the process diagram.
In the End Properties dialog, click inside the Work status cell and then use the down-arrow to select Resolved-Rejected from the list.
Click OK to close the End Properties dialog. Save updates to the flow image and then Close the Resolve-Reject process diagram tab. Save updates to the case type. Not all candidates would need to tour the company and it is up to the discretion of the HR person to start this process.
Approach Configure your solution to reference an optional process named Schedule Company Tour in the Interview stage. Hints Optional processes are configured at the stage level under Configure stage behaviors.
Optional processes are displayed as steps in the outline view of the stage. Hover over the Interview stage name until the down-arrow appears. Click to open the drop-down menu and select Configure stage behaviors. Save the flow record without making any changes and then Close the Flow process diagram tab ignore any draft mode warning. Open the Interview stage in the process outline and select the ScheduleCompanyTour step. If the flow action does not have a name, give it the name Schedule Company Tour and then click Configure form.
Use the Run process button to create a new case. Advance the case to the Qualify stage and then click the link to start the Conduct telephone interview step. Advance to the Interview stage. Select Add Work from the Other actions menu to see the newly created process. First, once a candidate has been selected for an open position, HR wants to notify the candidate by email. Second, if a candidate is rejected by a recruiter during the Qualification stage, the case should be redirected to the Post Rejection alternate stage.
Approach Convert the Notify Candidate step to a process that contains a Send Email smart shape configured to send an email to the candidate with the following information. Update the Determine Target Position flow with a Change Stage smart shape added to the Rejected connector, to direct the case to the Post Rejection stage.
To send the email to the Candidate, reference the Email property on the Candidate page. Test your changes by creating a new case and resolving it. Verify that the generated email is attached to the case as an attachment. Open the attachment and verify the contents. Ignore the error, which results from not configuring an email server.
Procedure Part 1 of 3 Send email to candidate with job offer Follow the steps below: Open the Step Configuration dialog for the Notify Candidate step and change it to a multi-step process. Open the process diagram for the Notify Candidate step in the process outline, and delete all of the assignments and resulting orphan connectors. Add a Send Email smart shape to the process. Open the properties panel for the Send Email smart shape. In the To field, reference the Email property on the Candidate page.
Note that you can confirm the property name using the Application Explorer. Click OK to close the form. Disable draft mode and Save updates to the flow. Test the flow by creating a new case and advancing to completion. Once you complete the case, review the generated email, which is added to the case as an attachment. Open the attachment and verify its contents. Ignore the exception that you see in the email attachment; this error indicates that the email cannot be sent to the person.
This is expected behavior since we have not configured an email server and account that can send outgoing emails. Part 2 of 3 Change Stage if Candidate does not qualify for a Position Follow the steps below to enter the Post Rejection stage if the candidate does not qualify for a position. Open the Determine Target Position process diagram in the process outline.
Add a Change Stage smart shape to the process, between the Rejected connector and the end shape. Right-click and View properties for the Change Stage shape. When the Change Stage dialog appears name the utility shape, click Select a stage, select the Post Rejection stage from the drop-down list, and enter an audit note.
Set Work Status to Resolved-Rejected. Click OK to close the End Properties dialog and view the resulting flow. Notice the new name in the Change Stage shape and the icon indicating the Resolved status. Test the flow by creating a new case. Advance to the Screen Candidate step. In the Screener Feedback field, select Does not match any position to reject the candidate. Verify that the case advances to the Post Rejection stage and the status is set to Resolved-Rejected.
Part 3 of 3 Change Stage if Candidate does not meet standards Follow the steps below: Open the Assess Candidate process diagram in the process outline. Add a Change Stage smart shape to the process, between the not qualified result and the end shape. When the Change Stage dialog appears click Select a stage, select the Post Rejection stage from the drop-down list, and enter an audit note.
Save changes to the case type and then test the flow by creating a new case and advancing to candidate scoring to determine a candidate is not qualified. Exercise: Set Goal and Deadline Intervals for a Case Scenario To ensure that SAE Corp does not acquire a negative perception with outside recruiters and prospective employees, the VP of HR wants to ensure that all applications for employment are resolved within a reasonable timeframe.
Historically, SAE Corp has resolved applications for employment with either a yes or no answer within 6 weeks 42 days. The VP wants to shorten the process by one week, and has requested a deadline of 5 weeks 35 days. In addition, the VP would like establish a goal to resolve applications within 3 weeks 21 days. Approach Establish a goal interval of 21 days and a deadline interval of 35 days for the Candidate case type, using the Details tab of the Case Designer.
Hints Goal and deadline intervals are set in the same dialog, accessed by clicking the Edit link to the right of the Goals and Deadlines entry on the Details tab of the Case Designer.
Goal and Deadline information for a case are displayed below the form for the current assignment. Click the Details tab and then click the Edit link to the right of Goals and Deadlines. In the Case Designer: Goals and Deadlines dialog, confirm that the goal and deadline interval are calculated from the start of the current Candidate case.
Under Goal Time from Start, enter 21 in the Days field. Under Deadline Time from Start, enter 35 in the Days field. Create a new Candidate case. Scroll down below the Personal Info form to view Case Details and verify that the Goal and Deadline times are calculated correctly.
Exercise: Document an Application Scenario During each phase of the development process, we need to document our application. This helps other individuals to understand the changes in the application since documentation was last generated.
.
Vree Building peag Application Defining the Process Defining the Data Elements Enhancing the User Interface Accessing Data in the Application Automating Business Policies Advanced Case Processing Documenting the Application Exercise: Use Designer Studio to Create and Process a Case Scenario Before we can begin to implement продолжение здесь solution, we need to understand how users create, process, and resolve cases using Pega 7.
Understanding how users perform their assignments helps по ссылке to determine how to implement an application and create, modify, and test its elements. In this exercise, you will perform three different roles, as listed in the table below. Approach The login credentials provided in the scenario will open an Employee Reimbursements demo application with an Expense Voucher case type.
In the Expense Voucher case, an employee fills out a voucher listing expenses. The manager determines if the expense will be approved or rejected and then notifies the employee of the final voucher status. To view the case type from each role, you will: Procedure Launch the exercise system, if ссылка на страницу is not already fref.
Then, follow the pega prpc video tutorial free download below to practice using Pega 7 from three different roles. On the Login screen, enter the employee username User MainCo and /30119.php shown in the Scenario section to log into the Employee Reimbursements application.
Complete and submit an expense voucher. Note: Ensure that you create at least two expense voucher cases so that you can approve and reject from the finance staff member role. On the Login screen, enter the manager username Manager MainCo and password shown in the Scenario section to log into the Employee Reimbursements application. View work items listed in the work basket, under the heading My Worklist. Click a blue highlighted ID link to open ;rpc expense voucher case.
Review pega prpc video tutorial free download voucher and click Submit to approve it. Open another dowbload and select Reject from the Other actions menu in the top-right of the screen. Notice that once youve opened the Reject screen, you can use the Other actions menu to return to the Approve screen. To view the remaining open cases, doenload Dashboard or My WorkList from choices on the left. To update the list, click Refresh list on the My WorkList screen.
Fill out all required forms and click Submit to advance the case to the Review Expenses stage. The dpwnload step is ffee in blue and you can see that the approval step has been assigned to a Manager.
From the Other actions menu, you can select to approve or reject this step 26 Since our system is not set up to deliver email, the administrator will receive an notice when mail delivery is attempted. Pega prpc video tutorial free download Create the HR Services Application Scenario Before we can begin to model processes, develop UIs, and implement a data model dodnload necessary parts of our pega prpc video tutorial free download we must create the application itself.
This basic structure will accommodate all of our work to implement the Candidate case. After collecting basic information about the application pega prpc video tutorial free download need to implement, the wizard creates the base elements and structure of our application, upon which we can implement the feee, policies, user interfaces and data needed to manage Candidate cases from start to finish.
For this exercise, tuyorial ignore some of the functionality of the wizard and focus solely on the steps that are necessary to create our application. Approach Run the New Application wizard and provide the following information to create an application: 23 Basic application information, such as the name and description of the application.
Note: Failure to enter certain information as specified will cause the wizard to create items whose names and behaviors differ from the names and behaviors assumed in later lessons. To avoid confusion and potential errors, use the following table to enter values in the appropriate field tutofial the wizard, and verify all pega prpc video tutorial free download before completing the wizard and creating your application.
Employees can use this application to manage candidate applications for dowlnoad positions within the company. Procedure Follow the steps below to create a new application: 23 Log in as a System Architect using the login credentials in the Scenario section.
As the new application is created, operator IDs, based on this organization name, will be created. Reuse layer:Implementation Click Application Settings to return to the first нажмите чтобы узнать больше of the pega prpc video tutorial free download, and review the information provided at each step. Errors in pega prpc video tutorial free download information may cause your application to behave in an unexpected manner, so be sure to confirm that the dowlnoad you have entered is correct and matches the table in the Farm frenzy 3 download full version pc kickass section of this lab exercise.
As part of the creation process, the system generates the following operators for your organization. Note that the organization will match the organization name you entered in Step 1 of the Application Creation Wizard. Log off and log back in using the administrator account created with the new application. After creating a new application, the operators default access group changes to that of the administrator for the new organization.
This access group may downloa have the role necessary to create another application. To run the Application Creation Wizard App Express again, ensure that your operator is in an access group that has /49559.php application viedo role.
Do this by selecting Switch Application from the application menu. Exercise: Add Stages to a Case Scenario Once a Lead System Architect runs the New Application wizard to create a starting point for our application, we can begin creating and configuring the elements that will comprise our eventual solution. The first step in this process pega prpc video tutorial free download to create stages for our case.
When working with a case, both end users and developers pepc it читать to identify the stages that make up the workflow of the case. These stages provide valuable context for application designers, who can use them frew organize the tasks and processes that comprise their case. They also provide valuable context for end users, who can use stages to measure the progress of a case as they process it. Procedure 1. Open the Case Explorer and select the Candidate case. Note: If you dont see the explorer menus, click the icon to the left of the Pega 7 logo to open the explorer panel in the Designer Pegw portal.
Add another stage named Decision. Note: To drag a stage, hover over the stage number until the cursor changes to a four-arrow icon and then click-and-drag. Vree Save to save changes to the case type. Exercise: Add Steps to a Hutorial Stage Scenario Once we divide a case into stages, the next step is to add steps to each stage. Each step represents a specific action or item to complete in order to process and ultimately resolve a case.
It serves to illustrate where students tutodial extend this application with the functionality implemented in System Architect Essentials II. Посмотреть больше Configure the Candidate case to include the steps listed in the Scenario. Hints By default, each step represents a single-step assignment. To change a step to a multi-step process, hover your mouse pointer over the step name, click the frew arrow icon, and select Configure step behaviors to open the Step Configuration dialog.
To configure a step to be available when the case enters a stage, open the Pega prpc video tutorial free download Configuration dialog for that step and select upon stage entry. Under the Collect Information stage, click Default Step. In the resulting tutorixl field, enter Personal Info. Hover your mouse pointer over the Determine Target Position step, click the down arrow icon, and select Configure нажмите для продолжения behaviors ptpc open the Step Configuration dialog.
Note the warning that the step type change is not reversible and then click OK to close the dialog. Open the Step Configuration dialog for было terminal emulator windows download free гонят Assess Candidate step.
Set the Step type to Download starter.exe Step Process, and configure the step to start upon stage entry. Click OK to vido the change. Exercise: Configure Assignments with the Process Outline Scenario During case elaboration, system architects work with business analysts and subject matter experts to decompose cases into processes, and processes посоветовали srs plugin for windows media player free download извиняюсь steps.
This allows business analysts and subject matter experts to decide on an application design that satisfies downloav pega prpc video tutorial free download of the business, and provides application designers with an approved design and set of specifications that they can use адрес страницы implement solution functionality. To properly decompose a case, we begin by dividing the case into stages, which we can then populate with steps.
Once we establish the steps needed to process and resolve a case, we dowmload model the processes that each step represents. Vudeo our processes allows us to establish the correct order for the tutodial that we know need to be performed, and results in a set of assignments and process flows that pega prpc video tutorial free download can test and verify against business expectations.
In addition, we can use our process model to help develop a set of draft user interfaces UIs and establish a data model. This is the first frre of the exercise. Hints The Process Outline displays either a process diagram for multi-step processes or a battlestations pacific download pc free panel for single-step assignmentsdepending upon the configuration of the corresponding step. Procedure Follow the steps below: If necessary, return to the Stage Designer. Hover over the first primary stage Collect Information viddeo click Pepc Process Detail when it appears.
The Process Outline appears, and displays the properties panel for the Personal Info assignment. The action is given a default name that is based on the step name.
Change the action name to Collect Personal Info and then scroll down to the Advanced section. Expand Assignment Details and enter the text Enter personal information. Click Save. Repeat step 3 for the remaining assignments in the Collect Information stage. Update the flow action name and add instructions from the following table.
Remember to Save after each update. Configure the assignments in the Qualify stage, using information from the following table. Configure the источник in the Interview stage, using information from the tutorail table.
Click Run to start a Candidate Case process, and verify that a message appears to inform you when an input form for an assignment step has not yet been created. Click No thanks, maybe later to fee testing process flow. Further down on the form, verify that the instruction you entered appears in the worklist, then click Submit.
Continue clicking No thanks, maybe later to verify the flow action message and instructions for each step.
No comments:
Post a Comment