End date to be set no more than certain days

[Mukul]

Hi All,

We have configured ARS to request for entitlements with start / end date. Because user can select the end date we don't want user to select a date which is way too far in future.

Is there a way to restrict user selecting an end date on the entitlement within certain time frame?

e.g lets say if start date is 10/10/2023 the end date can't be more than 10/10/2024

Regards.

-Mukul

[SumathiSomala]

@Mukul  Configure Config JSON for Request Dates in Entitlement type details page

{
"ENDDATEREQUIRED": "1",
"DEFAULTTIMEFRAMEHRS": "x",
"MAXTIMEFRAMEHRS": "3"
}

Viewing or Updating Endpoints (saviyntcloud.com)

[rushikeshvartak]

You can restrict based on hours in entitlement type configuration page 

Config JSON for Request Dates

Specify the configuration in the JSON format to display the Request Date option when an user requests for an entitlement type. Sample JSON: JSON { "ENDDATEREQUIRED": "1", "DEFAULTTIMEFRAMEHRS": "X", "MAXTIMEFRAMEHRS": "3" } where MAXTIMEFRAMEHRS specifies the maximum duration for raising an entitlement request.

Link : https://docs.saviyntcloud.com/bundle/EIC-Admin-v23x/page/Content/Chapter02-Identity-Repository/Viewi...

[Mukul]

Hi @rushikeshvartak and @SumathiSomala I tried the below config.. Had a look at the doc. The Defaulttime is working however I am still able to request beyond the MAXTimeFrame. See screen shots attached

[rushikeshvartak]

• what is config under endpoint for "Entitlement Filter Query for Request Start/End Date"
• Did you done restart after config ?

[rushikeshvartak]

Is this resolved @Mukul 

[Mukul]

• what is config under endpoint for "Entitlement Filter Query for Request Start/End Date"
  • Mukul : Nothing
• Did you done restart after config ?
  • yes

[rushikeshvartak]

What is request option for ent type

[Mukul]

Request Option is set to Table

[Kaushik]

Did you get any solution? I am also facing same issue.

I have set {"ENDDATEREQUIRED" : "1", "DEFAULTTIMEFRAMEHRS": "X", "MAXTIMEFRAMEHRS": "3"} but still the end date can be set to any future date.

[rushikeshvartak]

Change X to number

[Kaushik]

What is the difference between DEFAULTTIMEFRAMEHRS and MAXTIMEFRAMEHRS ?

I am expecting that if Start Date is 16 Feb 10.30 am then user should be allowed to select till 16 Feb 1.30 pm as End Date since I have set "MAXTIMEFRAMEHRS": "3" - is this understanding correct ??

[rushikeshvartak]

Default means by default how much hours to selected in end date and max means how much max is allowed

[Kaushik]

After I set Config JSON for Request Dates = { "ENDDATEREQUIRED" : "1", "DEFAULTTIMEFRAMEHRS": "1", "MAXTIMEFRAMEHRS": "3"} - if Start Date is 19 Feb 10.30 am, then by default end is shown as 19 Feb 11.30 am which is expected behavior but I can still select any end time like 10.30 pm which means MAXTIMEFRAMEHRS is not working correctly.

How to fix this ??

[rushikeshvartak]

Remove MAXTIMEFRAMEHRS  and check 

[Kaushik]

I guess you misunderstood my reply.

DEFAULTTIMEFRAMEHRS is working fine.

MAXTIMEFRAMEHRS is not working because I can still select any time beyond 3 hrs from start time.

[rushikeshvartak]

MAXTIMEFRAMEHRS - seems defect raise support ticket

[Kaushik]

MAXTIMEFRAMEHRS is working.

The error message shows up before final Submit during request creation - please refer attached screenshot but the error message mentions "should not be greater than <MAXTIMEFRAMEHRS>" instead of showing 3 hours 

Is this a bug ??

[rushikeshvartak]

Currently message is not dynamic attribute it will be implemented in future release updates on idea raised by me previously 

https://ideas.saviynt.com/ideas/EIC-I-4633