AnsweredAssumed Answered

Hidden Required Fields Are Now Evaulated with 7.0.0 P04

Question asked by Cynthia Gravely on Jan 20, 2017
Latest reply on Jan 23, 2017 by Cynthia Gravely

Like • Show 0 Likes0
Comment • 5

Our environment was upgraded from RSA 7.0.0 Patch 3 to Patch 5. An error is now generated and the form cannot be submitted for one of our applications. This appears to be due to a bug fix in Patch 4, "SF-775755 ACM-61928 Required entitlement field in Access Request form is empty, but form is still submitted."

I am looking for ideas as to how to create a new form. The requirement is that a user MUST select at least one Case Queue. The problem is that the available Case Queues displayed are based on the user's Profile. There are 3 Entitlement Table fields and each has a different display based on the Profile that is selected in the form. These 3 Entitlement Table fields were all marked as "Required", but that is no longer an options.

No one else has this question

Outcomes

5 Replies

Frank Schubert Jan 21, 2017 5:08 AM
Mark Correct
Correct Answer
Hi there,

would it be possible to filter the entitlement table based on e.g. the user's identity attributes? So have one entitlement table (required checked) instead of three. Or maybe a drop down list that gets used as a filter?

Regards

Frank
Like • Show 0 Likes0
Actions
- Cynthia Gravely @ Frank Schubert on Jan 22, 2017 1:18 PM
  Mark Correct
  Correct Answer
  I like this approach and am going to continue trying to think of a way to include all 3 scenarios into ONE filter. Unfortunately, the identity attributes aren't related to the filter. The entitlements presented are based on the Request Type the user selects.
  
  These are the 3 selections I am currently using based on the selection of 1 of 6 Request Types:
  
  1. Request Type = HR Agent, HR Agent Supervisor, or HR Systems Agent
  Set ReqType variable to "HR"
  Filter for Entitlement Table:
  x.Type='Queue'
  and x."Entitlement Raw Name" like 'HR%'
  and x."Entitlement Raw Name" not like '%L_D%'
  and x."Entitlement Raw Name" not like '%Payroll%'
  Display: ReqType = HR
  
  2. Request Type = HR Global Learning Agent
  Set ReqType variable to "LD"
  Filter for Entitlement Table:
  x.Type='Queue' and
  (x."Entitlement Raw Name" like 'HR%'
  and x."Entitlement Raw Name" like '%L_D%'
  Display: ReqType = LD
  
  3. Request Type = HR Payroll Agent or HR Payroll Supervisor
  Set ReqType variable to "PR"
  Filter for Entitlement Table:
  x.Type='Queue'
  and x."Entitlement Raw Name" like 'HR%'
  and x."Entitlement Raw Name" like '%Payroll%'
  Display: ReqType = PR
  
  This ReqType variable is set using a javascript block:
  $( "#hritProfile" ).change(function(){
  var prof=$( "#hritProfile option:selected").text();
  if(prof === "HR Global Learning Agent"){
  var rt = "LD";
  }else if(prof.indexOf("Payroll") !== -1){
  var rt = "PR";
  }else{
  var rt = "HR";
  }
  avform.setValue("ReqType",rt);
  });
  Like • Show 0 Likes0
  Actions
Mostafa Helmy Jan 21, 2017 9:03 AM
Mark Correct
Correct Answer
Hi Cynthia, would you consider using the "Display" tab for hiding the empty entitlement tables rather than the "Hide table if empty" check box? I believe if you mark a field as required but it is hidden due to a condition from the "Display" tab, you can still submit a form.
Like • Show 0 Likes0
Actions
- Cynthia Gravely @ Mostafa Helmy on Jan 22, 2017 11:55 AM
  Mark Correct
  Correct Answer
  Yes, that is how it was set up and stopped working after applying 7.0.0 P04. The bug that was fixed, "Required entitlement field in Access Request form is empty, but form is still submitted" now looks at the hidden fields due to a condition from the "Display" tab. Maybe this was not the intended behavior when the bug was fixed?
  Like • Show 0 Likes0
  Actions
Cynthia Gravely Jan 23, 2017 9:21 AM
Mark Correct
Correct Answer
I created 2 new variables, NotRT1 and NotRT2. The ReqType javascript block is updated so that each variable is populated depending on the selection, for example:

ReqType = HR
NotRT1 = Payroll
NotRT2 = L_D

I now how a generic filter:
x.Type='Queue'
and x."Entitlement Raw Name" like '%${avform.ReqType}%'
and x."Entitlement Raw Name" not like '%${avform.NotRT1}%'
and x."Entitlement Raw Name" not like '%${avform.NotRT2}%'

I'm seeing inconsistent behavior. If I change the Request Type on the form, most of the time, the entitlement table is updated correctly. However, sometimes it seems that it isn't clearing out the results of the previous filter.

Any thoughts on how I can make sure the previous results are cleared and the new results are displayed?
Like • Show 0 Likes0
Actions

Hidden Required Fields Are Now Evaulated with 7.0.0 P04

Outcomes

Related Content

Recommended Content