7 Replies Latest reply: Sep 29, 2011 9:45 AM by Carl Wilson RSS

Hidding entry points per view (and not per form)

Björn Calabuig

Hi List,

I'm facing a problem right now!

 

User Password changes has several views but I want to hide the entry point on Home Page only for one view (not to the entire views).

Configuration seems impossible! If you uncheck the entry point it seems to apply to the form, not for the selected view!!!

 

Can this been achieved? Maybe through workflow?

 

Kind Regards,

Björn.

  • 1. Re: Hidding entry points per view (and not per form)
    satyabrat6

    Hi Bjorn

    Do u know the exact use of appsubset Field which is present in the home page and whose ID is 1576.

    I thought the appsubset field and the VUI keyword ll help u.

    For deployable application we can display a subset of application and entry points to users by creating workflows.

    In the default home page form installed with AR System, there is a hidden reserve field named AppSubset(Field ID 1576) . we only need to add the necessary workflow to use it.

  • 2. Re: Hidding entry points per view (and not per form)
    satyabrat6

    If u want to restrict the changes for the particular view then u just write an Active Link and in the Run If Qualification write the condition as $VUI$="particular view name". It ll reflect the changes for the particular view not for the whole form.

    thanx

  • 3. Hidding entry points per view (and not per form)
    Björn Calabuig

    Thanks both,

    I found finally also the appsubset field

     

    I have a form called "F01:XXX", it's not an application itself, but it's present on the Home Page.

    I'm not getting the right sentence to fill the appsubset field:

     

    servername.F01:XXX? or "servername.F01:XXX" or...

     

    Once appsubset is loaded I do a PERFORM-ACTION-HOME-FIELD-REFRESH action.

    The AL fires on windows open but I'm getting an error:

     

    Error generating application list field content. (ARERR 1900)

     

    Any idea?

     

    Kind Regards,

    Björn.

     

     

     

     

     

     

     

     

     

     

     

     

  • 4. Re: Hidding entry points per view (and not per form)
    satyabrat6

    Yes Bjorn

    you are right...the appsubset field is for setting the entry points for the particular application.

    As "F01:XXX" is a form u dont have to use it in appsubset field. But according to ur query i just try the solution now.

  • 5. Hidding entry points per view (and not per form)
    satyabrat6

    Hi Bjorn

    Can u share the exact requirement of ur problem?

    The form is a regular form or Display only form?

    How many views associated with that form?

    You said tha u want to hide the entry point for one view not to the entire view....so can we set entry point for different views?

  • 6. Re: Hidding entry points per view (and not per form)
    Björn Calabuig

    This is my Home Page:

     

    Home001.jpg

     

    There's an entry point called Change Password, that opens this form:

    Home002.jpg

    Change password has been localized to several locales (a view for each locale).

    I need to hide the entry point for only one locale and show it for all others.

     

    BUT, entry points work at form level, and NOT at view level (unless I'm wrong)

     

    So, how to achieve this? I found appsubset, but I'm focusing many problems to get the right syntax to populate the aforementioned field with the entry points I want to be shown for that specific view.

     

    This is my problem and I think the only solution is using appsubset.

     

    I'm testing right now with an AL that perform the Home Page refresh (I'm entering manualluy just one entry point, let's say servername.Change Password or servername.Change\ Password or "servername.Change Password",...

     

    No results, only ARERR 1900.

     

    Thanks for your help. Hope you get now my point of view, maybe I'm wrong and appsuset only works with deployable apps, but if I'm not wrong Approval Central or Change Password are NOT apps, are simply forms... Anyway if you try also with Application Administration Console, for example, I'm getting the same result.

     

    Kind Regards,

    Björn.

  • 7. Re: Hidding entry points per view (and not per form)
    Carl Wilson

    Hi Björn,

    a crude way to do this would be to create a "cover" for this application point such as a button that becomes un-hidden for this particular locale.  You can then change the colours to be the same as the app list background.  It would be assumed the entry point would be in the same location for all users for this to work.  Crude but simple to implement.

     

    Another way could be to make this into a Deployable app with the one (or more) forms, although it would probably require a lot more work to for this one requirement.  Then you could utilise the functionality above.

     

    The other options are all overkill, such as creating a separate view and manually built app list with Active Links to open the entry points, etc.

     

    So, a few options but probably not the simple solution you were looking for.