Skip to Content
avatar image
Former Member

Firefighter Validity Dates in Access Request

Currently we have configured the configuration parameter 4001 to 1 day,but the user(firefighter) submits a GRC access access for firefighter ID,he/she can change the valid to date,is there anyway we can restrict the valid to date in the firefighter access request screen,I thought of creating a EUP only for Req Type EAM(006),But I can't find the Valid from & Valid To dates in EUP?

Information on 4001 parameter.

4001 (Default Firefighter Validity Period (Days)): When you provide valid from and valid to dates as you assign a Firefighter Role or Firefighter ID to a Firefighter, these dates will be applied to the assignment, overriding the Default Firefighter Validity Period setting. Initially the Firefighter ID or Role assigned is from the current date. When you
omit the โ€œto dateโ€ and you have not set Default Firefighter Validity Period, the assignment will be active until 12/31/9999. When you omit the to date and you have set a Default Firefighter Validity Period, then the assignment you are assigning will remain active until the current date, plus the number of days you specified for the Default Firefighter Validity Period

Can anyone faced with similar issue,then can you please guide me so that we will not give user(firefighter) ability to change the valid to date.

Thanks

Ramesh

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

3 Answers

  • Mar 19, 2015 at 12:11 PM

    Hi Ramesh,

    I suggest you to enable the settings at approver stage to change VALIDITY dates by the Firefighter owner in case user submits wrongly.

    You can highlight this as audit concern if FF ID is given to the users for more than certain period of time and tell your FF Owners to check validity dates before approving FF access requests.

    If you just make VALIDITY dates fields as READ ONLY using Webdynpro customization in Admin mode it gets applicable to all access request types.

    We did the same as suggested for you as part of our training and we found there are cases where users are changing validity dates for FF access when submitting and FF owners are correcting the dates before approval for few cases and rejecting for few cases ๐Ÿ˜Š

    Regards,

    Madhu.

    Add comment
    10|10000 characters needed characters exceeded

  • Mar 19, 2015 at 08:19 AM

    Dear Ramesh,

    parameter 4001 only delivers the default period. You can override the validity period for each assignment in the access request.

    What you can do is manually change your views so that this field is read-only.

    Regards,

    Alessandro

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Mar 19, 2015 at 04:29 PM

    Thank you Madhu & Alessandro for your valid inputs.

    "If you just make VALIDITY dates fields as READ ONLY using Webdynpro customization in Admin mode it gets applicable to all access request types"

    This is what I am more concerned about,If it applies to all req types then its not a valid solution,It should apply to only Re type : 006(EAM).

    But Yes I agree with the manual approach for the FF Owner to double check before approving the request.

    Thanks

    Ramesh

    Add comment
    10|10000 characters needed characters exceeded