Hi,

Maybe you can make a filter in FORM:A that pushes the record into FORM:B.
The user would then modify the FORM:A record, presumably setting a couple
of display-only-fields that will be sent on to FORM:B.

A Push-Fields in a filter has Admin-permissions.

        Best Regards - Misi, RRR AB, http://www.rrr.se (ARSList MVP 2011)

Products from RRR Scandinavia (Best R.O.I. Award at WWRUG10/11):
* RRR|License - Not enough Remedy licenses? Save money by optimizing.
* RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs.
Find these products, and many free tools and utilities, at http://rrr.se.

> Hi listers,
>
> I have a problem that I've solved, but I think that there is an easier
> (and
> more elegant) solution that the one I developed. Here's my case:
>
> I have two forms:
>
> FORM:A
> FORM:B
>
> Both forms are related, so 1 request in FORM:A is related to many requests
> in FORM:B. I have a table in FORM:A listing the related requests in
> FORM:B.
>
> The permissions scheme is very complex and I have a field with ID 60100
> and
> a dynamic group with the same ID. A super-user can create requests in
> FORM:A and the field 60100 is populated with the list of groups that have
> the write access granted. Similary, I have field with ID 60200 that is
> related to the read access to the request. FROM:B works in the same way.
>
> The requisition is the next: Imagine a user John_Doe that has write access
> to one request in FORM:A and isn't a super-user. He must be able to create
> request in FORM:B related to the request in FORM:A that is related.
>
> I normally copy fields 60100 and 60200 from FORM:A to FORM:B, to propagate
> the permissions. But at submit, these dynamic groups doesn't exist yet, so
> I get an access error. I can bypass it allowing any user to submit, but
> any
> user will be able to create requests in FORM:B, and I don't want that. So
> I
> created a filter that checks that the user belongs to a group listed in
> field 60100. If field 60100 has only one group is very easy to do, but if
> 60100 can hold a set of groups, then I need to create a guide, separate
> all
> groups present in field 60100 and check each one separately.
>
> I've done it and it works, but I'm convinced that there must be an easier
> way to do it. Any idea?
>
> Jose M. Huerta
> Project Manager**
>
> Movil: 661 665 088
>
> Telf.: 971 75 03 24****
>
> Fax: 971 75 07 94****
>
>  <http://www.sm2baleares.es/>****
>
> SM2 Baleares S.A.
> C/Rita Levi ****
>
> Edificio SM2 Parc Bit****
>
> 07121 Palma de Mallorca****
>
>           <http://es-es.facebook.com/pages/SM2-Baleares/158608627954>
>   <http://twitter.com/#!/SM2Baleares>
>      <http://www.linkedin.com/company/sm2-baleares>
>
> La información contenida en este mensaje de correo electrónico es
> confidencial. La misma, es enviada con la intención de que únicamente sea
> leída por la persona(s) a la(s) que va dirigida. El acceso a este mensaje
> por otras personas no está autorizado, por lo que en tal caso, le rogamos
> que nos lo comunique por la misma vía, se abstenga de realizar copias del
> mensaje o remitirlo o entregarlo a otra persona y proceda a borrarlo de
> inmediato.****
>
> P Por favor, no imprima este mensaje ni sus documentos adjuntos si no es
> necesario.
>
> _______________________________________________________________________________
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
> attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
>

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"

Reply via email to