Lab 8: Populate Attributes and Create a Report · Enter a Condition of ErrorMessage == "Invalid...

Publishing to Case Management, Release 12.2.1

Page 71 of 96 Copyright ©

Lab 8: Populate Attributes and Create a ReportYou have generated cases and alerts. Well done. Now it is time to refine your solution a little more.There are two aims in this lab:

1. Populate the Priority field for alerts You may have noticed that all alerts (and cases come to that) already have a Priority field. This is because Priority is one of Case Management’s builtpriority field is currently set to

2. Create a report that displays alerts by error message.

In this lab you will create something called a Parameter (this will be called Parameters are configured in workflows. will be able to pass the value of the Error data stream’s ErrorMessage parameter. You configure the parameter mappingDirector, via the match processor’s Advanced Options)creating two Reception Rules in your Alerts Workflow to set the Priority field to the value in the parameter. Reception Rules can set the value of an attribute or extended attribute or transition cases and alerts to different states basIn the first reception rule you will stipulate that where the error message is Format, the Priority should be set to where the error message is Invalid Value in UMCODE

Next, you will need to create something called an Extended Attribute defined attribute that is displayed against alerts and which can be used in reportattribute will be called Error Messageable to pass the value of the parameter into the extended attribute by creating a Reception Rulepart of your Alerts workflow. You wilattribute in a report. And this will enable you to create your alerts by error message report.

Copyright © 2015, Oracle and/or its affiliates. All rights reserved.

Attributes and Create a ReportYou have generated cases and alerts. Well done. Now it is time to refine your solution a little more.

field for alerts with one of two values: High or Medium

You may have noticed that all alerts (and cases come to that) already have a Priority field. This is because Priority is one of Case Management’s built-in attributes. However, the priority field is currently set to None:

rt that displays alerts by error message.

create something called a Parameter (this will be called ErrorMessageworkflows. Having created your parameter in the Alerts Workflow,

the value of the Error data stream’s Error Message attribute into the . You configure the parameter mapping in the Case Source (i.e. in

Director, via the match processor’s Advanced Options). You can achieve your first aim simply by creating two Reception Rules in your Alerts Workflow to set the Priority field to a value based upon the value in the parameter. Reception Rules can set the value of an attribute or extended attribute or transition cases and alerts to different states based upon JavaScript or Groovy Script conditions. In the first reception rule you will stipulate that where the error message is Invalid PARTID

should be set to High. In your second reception rule you will stipulate thatInvalid Value in UMCODE, the Priority will be set to

Next, you will need to create something called an Extended Attribute - which is effectively a userdefined attribute that is displayed against alerts and which can be used in reports. Your extended

Error Message. Once you have created your extended attributeable to pass the value of the parameter into the extended attribute by creating a Reception Rule

You will also find that you can use your Error Messageattribute in a report. And this will enable you to create your alerts by error message report.

Attributes and Create a Report You have generated cases and alerts. Well done. Now it is time to refine your solution a little more.

Medium.

You may have noticed that all alerts (and cases come to that) already have a Priority field. in attributes. However, the

ErrorMessage). created your parameter in the Alerts Workflow, you

attribute into the in the Case Source (i.e. in

You can achieve your first aim simply by value based upon

the value in the parameter. Reception Rules can set the value of an attribute or extended attribute ed upon JavaScript or Groovy Script conditions.

Invalid PARTID . In your second reception rule you will stipulate that;

will be set to Medium.

which is effectively a user-s. Your extended

. Once you have created your extended attribute, you will be able to pass the value of the parameter into the extended attribute by creating a Reception Rule as

Error Message extended attribute in a report. And this will enable you to create your alerts by error message report.

Publishing to Case Mana

Copyright ©

Add a Parameter to Your Workflow1. Return to the Case Management Administration user interface.

1. Double-click Workflow Administration



Page

Add a Parameter to Your Workflow Return to the Case Management Administration user interface.

Workflow Administration. The Workflow Administration window will open.

Page 72 of 96

. The Workflow Administration window will open.



2. Double-click your Alerts Workflow

3. Navigate to the Parameters

4. Click . The Parameter window will open.

5. Enter a Name of ErrorMessage

6. Ensure that the Enabled? checkbox is selected and click

7. Click to save your workflow.

Map Your Parameter to a Field in the Incoming Data1. Return to the Director user interface.

2. In the Director UI’s Project Browser, already expanded, expand it, and, within that project, expand the

3. If it isn’t already open on the Management process to open it on the

4. On the canvas, double-click the


Alerts Workflow to open it in the Workflow Editor.

Parameters tab, which is near the bottom of the Workflow Editor.

indow will open.

Message

checkbox is selected and click OK.

to save your workflow.

Map Your Parameter to a Field in the Incoming Data Return to the Director user interface.

ect Browser, if your Case Management Training , and, within that project, expand the Processes

If it isn’t already open on the canvas, double-click the Audit and Publish Errors to Case pen it on the canvas.

click the Advanced Match processor to open it.

tab, which is near the bottom of the Workflow Editor.

project is not Processes node.

Audit and Publish Errors to Case

Publishing to Case Management

Copyright ©

5. Click the Advanced Options

The Options window will open.

6. In the Options window, navigate to the

The New Source Data window w



Page

Advanced Options link.

The Options window will open.

In the Options window, navigate to the Case Source tab and click .

The New Source Data window will open.

Page 74 of 96



7. Click Next > five times. You should reach the Parameter Mappings for Alert window.

8. In the Parameter Mappings for Alert window, you should see your new parameter. Select the ErrorMessage

9. In the Selection Function dropdown, choose

10. Click Add. The Add Select Input window will open.

11. In the Add Selection Input window, choose


five times. You should reach the Parameter Mappings for Alert window.

In the Parameter Mappings for Alert window, you should see your new ErrorMessageErrorMessage parameter and then check the Enabled

dropdown, choose First Non-Empty Value.

. The Add Select Input window will open.

In the Add Selection Input window, choose Error and click OK.

five times. You should reach the Parameter Mappings for Alert window.

ErrorMessage Enabled checkbox.


Copyright ©

12. In the Values dropdown, select

13. Click Finish to close the New Data Source window. You are returned to the Options window.

14. Click OK to close the options window.



Page

dropdown, select ErrorMessage.

se the New Data Source window. You are returned to the Options

to close the options window.

Page 76 of 96

se the New Data Source window. You are returned to the Options


7 of 96 Copyright ©

Populate the Priority Attribute1. Return to the Case Management Administration user interface.

2. Unless it is already open, doubleAdministration window will open.

3. Unless it is already open, doubleEditor.


Populate the Priority Attribute Return to the Case Management Administration user interface.

ouble-click Workflow Administration. The Workflow Administration window will open.

ouble-click your Alerts Workflow to open it in the Workflow

. The Workflow

to open it in the Workflow


Copyright ©

4. Navigate to the Reception tab, which is near the bottom of the Workflow Editor.

5. Click Add… The Action window will open.

6. Enter a Name of Set High Priority

7. Enter a Condition of ErrorMessage == "Invalid PARTID Format"

8. Click directly under the Attributes

9. In the Name drop-down select

10. In the Value drop-down select



Page


Action window will open.

Set High Priority.

ErrorMessage == "Invalid PARTID Format".

Attributes box. The New dialog will open.

down select Priority.

elect High.

Page 78 of 96




11. Click OK to close the New dialog.

12. Click OK to close the Action dialog.


14. Enter a Name of Set Medium

15. Enter a Condition of ErrorMessage == "Invalid

16. Click directly under the Attributes


to close the New dialog.

to close the Action dialog.

The Action window will open.

Medium Priority.

ErrorMessage == "Invalid Value in UMCODE".

Attributes box. The New dialog will open.


Copyright ©


18. In the Value drop-down select




Page

down select Priority.

down select Medium.


Page 80 of 96



20. Click OK to close the Action dialog.

21. Click to save your Alerts Workflow.

Bulk Delete Your Cases and AlertsYou may have noticed a Bulk Delete function near the top of the Case Management user interface:

This is a privileged function that deletes all cases and alerts currently listed by the filter. Your user, dnadmin, is able to Bulk Delete because it is a member of the Administrators user group. Typically, very few Case Management users will have access to this function since, in a production environment, it can be dangerous. It is, however, useful during development. For example, let’s say that you configure your Case Source, look at the results in the Case Management UI, and then decide that you want your configuration to be radically different. You can select all of your cases and alerts, delete them in bulk, change your configurationregenerate the cases and alerts. This is a very useful tool during development. Since we have made a change to the configuration of both our Case Source, and one of our workflows, we will use it now.

1. Return to the Case Management user interface.

2. If you are still drilled-down on an alert, click

3. Navigate to the Filter tab (look near the bottom


to close the Action dialog.

to save your Alerts Workflow.

r Cases and Alerts You may have noticed a Bulk Delete function near the top of the Case Management user interface:

This is a privileged function that deletes all cases and alerts currently listed by the filter. Your user, because it is a member of the Administrators user group. Typically,

very few Case Management users will have access to this function since, in a production environment, it can be dangerous. It is, however, useful during development. For example, let’s say that you configure your Case Source, look at the results in the Case Management UI, and then decide that you want your configuration to be radically different. You can select all of your cases and alerts, delete them in bulk, change your configuration, and then run your process again to regenerate the cases and alerts. This is a very useful tool during development. Since we have made a change to the configuration of both our Case Source, and one of our workflows, we will use

e Management user interface.

down on an alert, click .

tab (look near the bottom-left of the screen for this).

You may have noticed a Bulk Delete function near the top of the Case Management user interface:

This is a privileged function that deletes all cases and alerts currently listed by the filter. Your user, because it is a member of the Administrators user group. Typically,

very few Case Management users will have access to this function since, in a production environment, it can be dangerous. It is, however, useful during development. For example, let’s say that you configure your Case Source, look at the results in the Case Management UI, and then decide that you want your configuration to be radically different. You can select all of your cases

, and then run your process again to regenerate the cases and alerts. This is a very useful tool during development. Since we have made a change to the configuration of both our Case Source, and one of our workflows, we will use


Copyright ©

4. In the Type box, select both the Ctrl button whilst clicking with your mouse).

5. In the Source box, select Errors

6. Click . All of the cases and alerts are displayed in a list.

7. Click .

8. A message may be displayed warning that the bulk operation will affect all cases that are relevant to the current selected filter. Click

9. A message will be displayed warning that the process may take some time (it won’t as we only have a small number of cases and alerts). Click

10. Near the top-left of the screen, click alerts, the list should now appear empty.

Run the Process 1. Return to the Director user interface.



Page

box, select both Case and Alert. (To select multiple items keep your finger on trl button whilst clicking with your mouse).

Errors.

. All of the cases and alerts are displayed in a list.

A message may be displayed warning that the bulk operation will affect all cases that are the current selected filter. Click OK.

A message will be displayed warning that the process may take some time (it won’t as we only have a small number of cases and alerts). Click OK to dismiss the message.

left of the screen, click . As you have deleted all of the cases and alerts, the list should now appear empty.

Return to the Director user interface.

Page 82 of 96

. (To select multiple items keep your finger on

A message may be displayed warning that the bulk operation will affect all cases that are

A message will be displayed warning that the process may take some time (it won’t as we to dismiss the message.

ou have deleted all of the cases and



2. In the Director UI’s Project Browser, if necessary expand your Training project, and, within that proje

3. Double-click the Audit and Publish Errors to Case Managementthe canvas.

4. In the toolbar at the top of the

5. Ensure that your process executes successfully. If it does Tasks window and the Event Log. Fix the problems you find, and then run the process again.

Examine Your Newly Populated Priority Attribute in the Case Management User Interface

1. Return to the Case Management user interfac

2. In the Type box, select Alert


4. Click . All of the alerts are displayed in a list.

5. Click the Priority column header to display the alerts in order of Priority ascending.

6. Confirm that all of your alerts now have a priority priority allocated is dependent on the error message.

A Note About flags.xml Your next task in this lab will be to create a new extended attributebe able to use your new extended attribute in reports. You called flags.xml. This file can be found in one or both of two locations:

• The casemanagement folder within your EDQ server’s

• The casemanagement folder within your EDQ server’s word local in this folder name).

In new installations of EDQ, you will only find flags.xml in the first of the(~oedq.home/casemanagement). This is the default location for


In the Director UI’s Project Browser, if necessary expand your Case Management project, and, within that project, expand the Processes node.

Audit and Publish Errors to Case Management process to open it on

In the toolbar at the top of the canvas, click to run your process.

Ensure that your process executes successfully. If it does not, investigate the errors in the Tasks window and the Event Log. Fix the problems you find, and then run the process

Examine Your Newly Populated Priority Attribute in the Case Management User Interface

Return to the Case Management user interface.

Alert only (do not select Case).

Errors.

. All of the alerts are displayed in a list.

column header to display the alerts in order of Priority ascending.

your alerts now have a priority – either Medium or High –priority allocated is dependent on the error message.

Your next task in this lab will be to create a new extended attribute called Error Messagele to use your new extended attribute in reports. You add extended attributes in an xml file

. This file can be found in one or both of two locations:

folder within your EDQ server’s oedq.home folder.

folder within your EDQ server’s oedq.local.home folder (note the in this folder name).

In new installations of EDQ, you will only find flags.xml in the first of these two locations (~oedq.home/casemanagement). This is the default location for the file. If you have installed

Case Management

process to open it on

not, investigate the errors in the Tasks window and the Event Log. Fix the problems you find, and then run the process

Examine Your Newly Populated Priority Attribute in the Case

column header to display the alerts in order of Priority ascending.

– and that the

Error Message. You will add extended attributes in an xml file

folder.

folder (note the

two locations the file. If you have installed



Page 84 of 96

Oracle Watchlist Screening on your EDQ server, this comes with its own version of flags.xml, which you will find at ~oedq.local.home/casemanagement (the second of the two locations listed above). And if you have made any changes to flags.xml in the past, then again you should have placed the changed file in ~oedq.local.home/casemanagement (again, the second of the two locations listed above).

This might seem a little confusing at first, but there is a good reason for it.

The key point to understand is that oedq.home contains a default set of configuration files (including flags.xml) that are provided with your EDQ distribution. If you upgrade your EDQ server to a new release, then the default files in oedq.home will be automatically replaced during the upgrade with fresh versions. So, if you made any changes in oedq.home, they will be lost. If you create tailored versions of any of the files in oedq.home (for example, flags.xml), then the tailored versions should be placed in the appropriate sub-folder of oedq.local.home. oedq.local.home is a safe location that will not be affected by upgrades. You should put your tailored configuration files in oedq.local.home safe in this knowledge. If the same configuration file exists in both oedq.home and oedq.local.home, the oedq.local.home version takes precedence (in fact, strictly-speaking, the EDQ server would see the two files as one big file, and the values from both would be used, except in cases of conflict, when the oedq.local.home values would be used). Many people find that the simplest approach is to move (not copy) a file from oedq.home to oedq.local.home when tailoring is required. This avoids any possible confusion about which version of the file is being used.

The EDQ-12.2.1-Trn virtual machine includes Oracle Watchlist Screening, which comes with a tailored version of flag.xml, which you will find in ~oedq.local.home/casemanagement. And in this training lab it is this tailored version in ~oedq.local.home/casemanagement that you will amend. Do bear in mind though, that if you carry out this exercise using a fresh installation of EDQ (for example, if you have installed EDQ on a Windows machine using the Quick Start installer), then you would not have a tailored version of flags.xml. You would therefore move flags.xml from ~oedq.home/casemanagement to ~oedq.local.home/casemanagement and make changes to it there.

Add an Extended Attribute to flags.xml Note that the instructions below assume that you are using the EDQ-12.2.1-

Trn virtual machine. If you are not using this virtual machine, you may have to adapt the instructions somewhat to accommodate the operating system

and folder locations on your EDQ server.

1. Within the EDQ-12.2.1-Trn virtual machine, navigate to this folder: /apps/oracle12_2_1/fmw/user_projects/domains/base_domain/config/fmwconfig/edq/oedq.local.home/casemanagement

To do this, move to the desktop of the virtual machine, and double click the Computer icon. Then, in the Computer window, double click the Filesystem icon and navigate through the file system until you reach the folder listed above.



2. Right-click flags.xml and select

The flags.xml file opens in a text editor.

3. Add the following line before the closing </f:flags> tag: <f:flag index="7" label="Error Message" type="string" readonly="true"/>


and select Open with > gedit.

The flags.xml file opens in a text editor.

Add the following line before the closing </f:flags> tag:

" label="Error Message" type="string" readonly="true"/>

" label="Error Message" type="string" readonly="true"/>


Copyright ©

4. Click to save your edited flags.xml file and close the text editor.

5. Return to the virtual machine’s desktop and double click the Terminal icon to open a terminal window.

6. Type restart-edq-app-serverkeyboard.

The edq application server will take several minutes to restart. Progress will be reported in the terminal window. When the application server has finished restart



Page

to save your edited flags.xml file and close the text editor.

Return to the virtual machine’s desktop and double click the Terminal icon to open a

server into the terminal window and hit the Enter key on your

The edq application server will take several minutes to restart. Progress will be reported in the terminal window. When the application server has finished restarting you will see this:

Page 86 of 96

Return to the virtual machine’s desktop and double click the Terminal icon to open a

into the terminal window and hit the Enter key on your

The edq application server will take several minutes to restart. Progress will be reported in ing you will see this:



Add a Reception Rule to Pass the Error Message from the Parameter to the Extended Attribute

1. If the Case Management Administration user interface is still open, close it, and then relaunch it from the Launchpad.

You need to close and reopen the Case Management Administration user

interface because you have restarted the EDQ application server.

2. Double-click Workflow Administration


Add a Reception Rule to Pass the Error Message from the Parameter to the Extended Attribute

If the Case Management Administration user interface is still open, close it, and then relaunch it from the Launchpad.

nd reopen the Case Management Administration user

interface because you have restarted the EDQ application server.

Workflow Administration. The Workflow Administration window will open.

Add a Reception Rule to Pass the Error Message from the Parameter

If the Case Management Administration user interface is still open, close it, and then

. The Workflow Administration window will open.


Copyright ©

3. Double-click your Alerts Workflow

4. Navigate to the Reception tab, which is near the bottom of the Workflow Editor.


6. Enter a Name of Populate Error Message Extended Attribute

7. Click directly under the Extended


9. Select the Parameter radio button, and, in the ErrorMessage.



Page

Alerts Workflow to open it in the Workflow Editor.


The Action window will open.

Error Message Extended Attribute.

Extended Attributes box. The New dialog will open.

down select Error Message.

radio button, and, in the Parameter drop-down select

Page 88 of 96


ew dialog will open.

down select




11. Click OK to close the Action dialog. You will be returned to th

12. Click to save your Alerts Workflow.

13. Close the Workflow Editor window.



to close the Action dialog. You will be returned to the Workflow Editor.

to save your Alerts Workflow.

Close the Workflow Editor window.

e Workflow Editor.


Copyright ©

Bulk Delete Your Cases and Alerts1. Return to the Case Management user interface.

2. The UI will have disconnected from the EDQ application server when the applicatiowas restarted, so click Login

3. Enter your Username and Passwordmachine, both the Username and Password are

4. Navigate to the Filter tab (look near the bottom

5. In the Type box, select both the Ctrl button whilst clicking with your mouse).


7. Click . All of the cases and alerts are displayed in a list.

8. Click .

9. A message may displayed warning you that the bulk operation will affect all cases that are relevant to the currently selected filter. Click

10. A message will be displayed warning that the process may take some time (it won’t as we only have a small number of cases and alerts). Click

11. Near the top-left of the screen, click alerts, the list should now appear empty.



Page

Bulk Delete Your Cases and Alerts Return to the Case Management user interface.

The UI will have disconnected from the EDQ application server when the applicatioLogin.

Password (if you are using the EDQ-12.2.1-Trn, both the Username and Password are dnadmin), and click OK.

tab (look near the bottom-left of the screen for this).

box, select both Case and Alert. (To select multiple items keep your finger on the Ctrl button whilst clicking with your mouse).

Errors.

. All of the cases and alerts are displayed in a list.

A message may displayed warning you that the bulk operation will affect all cases that are relevant to the currently selected filter. Click OK.

A message will be displayed warning that the process may take some time (it won’t as we mber of cases and alerts). Click OK to dismiss the message.

left of the screen, click . As you have deleted all of the cases and alerts, the list should now appear empty.

Page 90 of 96

The UI will have disconnected from the EDQ application server when the application server

Trn virtual

. (To select multiple items keep your finger on

A message may displayed warning you that the bulk operation will affect all cases that are

A message will be displayed warning that the process may take some time (it won’t as we to dismiss the message.

. As you have deleted all of the cases and



Run the Process 1. Return to the Director user interface.

2. The UI will have disconnected from the EDQ application server when the application server was restarted, so, in the Project Browser, rightConnect to Server.

3. When prompted, enter your credentials (if you are using the machine, the username and password are both

4. In the Director UI’s Project Browser, expand your and, within that project, expand the

5. Double-click the Audit and Publish Errors to Case Mthe canvas.

6. In the toolbar at the top of the

7. Ensure that your process executes successfully. If it does not, investigate the errors in the Tasks window and the Event Log. Fix the probleagain.


Return to the Director user interface.

have disconnected from the EDQ application server when the application server was restarted, so, in the Project Browser, right-click localhost (dnadmin)

When prompted, enter your credentials (if you are using the EDQ-12.2.1-Trnmachine, the username and password are both dnadmin).

In the Director UI’s Project Browser, expand your Case Management Trainingand, within that project, expand the Processes node.

Audit and Publish Errors to Case Management process

In the toolbar at the top of the canvas, click to run your process.

Ensure that your process executes successfully. If it does not, investigate the errors in the Tasks window and the Event Log. Fix the problems you find, and then run the process

have disconnected from the EDQ application server when the application server and select

Trn virtual

Case Management Training project,

process to open it on

Ensure that your process executes successfully. If it does not, investigate the errors in the ms you find, and then run the process


Copyright ©

Examine Your New Error Message Extended Management User Interface

1. Return to the Case Management user interface.

2. In the Type box, select Alert


4. Click . All of the alerts are displayed in a list.

5. Drill-Down on the first alert in the list.

6. In the Summary section, on the left side of the screen, confirm that the Error Message extended attribute has been populated

Note that you may see a different record to the one displayed in the

screenshot above.

Create an Alerts by Error Message Report

1. Click . In the Filter’s Source box, you should still have



Page

Error Message Extended Attributes in the Case Management User Interface

Return to the Case Management user interface.

Alert only (do not select Case).

Errors.

. All of the alerts are displayed in a list.

Down on the first alert in the list.

In the Summary section, on the left side of the screen, confirm that the Error Message extended attribute has been populated.

y see a different record to the one displayed in the

Create an Alerts by Error Message Report

. In the Filter’s Type box, you should still have Alert selected, and in the box, you should still have Errors selected. Leave these settings as they are.

Page 92 of 96

in the Case

In the Summary section, on the left side of the screen, confirm that the Error Message

selected, and in the hese settings as they are.



2. In the Filter, scroll-down if necessary and click section of the Filter.


down if necessary and click . This will open the Reporting

. This will open the Reporting


Copyright ©

3. In the Columns box select Priority

4. Click . The report is displayed.

The particular combination of attributes displayed is a little meaningless, since

all Invalid PARTID Format errors are High Priority and all Invalid Value in UMCODE errors are Medium Priority. The only reason for selecting both of

these is to illustrate that you can create reports with different extended attributes on the x and y axis.

lishing to Case Management, Release 12.2.1


Page

Priority, and in the Rows box select Error Message

. The report is displayed.

he particular combination of attributes displayed is a little meaningless, since

all Invalid PARTID Format errors are High Priority and all Invalid Value in UMCODE errors are Medium Priority. The only reason for selecting both of

at you can create reports with different attributes or on the x and y axis.

Page 94 of 96

Error Message.

he particular combination of attributes displayed is a little meaningless, since



Click the 112 High priority Invalid PARTID Format alerts.

Note that you the list displays the High Priority Invalid PARTID Format alerts.

5. Click .

Save Your Report

1. Click . The Save As dialog opens.

2. Enter a Name of Alerts by Error Message and Priority Report


High priority Invalid PARTID Format alerts.


The Save As dialog opens.

Alerts by Error Message and Priority Report and click


and click OK.


Copyright ©

3. Navigate to the Browser tab.

Note that your Alerts by Error Message and Priority

the Browser. You can returntime that you log in to the Case Management user interface).

4. In the Browser, note that your report is currentuser can access it.

5. Right-click your Alerts by Erromove your report to the global filters. Global reports and filters can be accessed by all of your EDQ instance’s Case Management users.

Note that being able to make reports and filters global is a privi

Your dnadmin user is an administrator, and so can make reports and filters global. However, in a production environment, this would typically be a

restricted function.



Page

tab.

Note that your Alerts by Error Message and Priority report has been saved in

the Browser. You can return to this report at any time (for example, the next time that you log in to the Case Management user interface).

In the Browser, note that your report is currently a User filter, which means that

Alerts by Error Message and Priority report, and note that you can move your report to the global filters. Global reports and filters can be accessed by all of your EDQ instance’s Case Management users.

Note that being able to make reports and filters global is a privileged function.

Your dnadmin user is an administrator, and so can make reports and filters global. However, in a production environment, this would typically be a

Page 96 of 96

eport has been saved in

to this report at any time (for example, the next

which means that only your

report, and note that you can move your report to the global filters. Global reports and filters can be accessed by all of

leged function.

Lab 8: Populate Attributes and Create a Report · Enter a Condition of ErrorMessage == "Invalid...

Documents

Transcript of Lab 8: Populate Attributes and Create a Report · Enter a Condition of ErrorMessage == "Invalid...