Re: ITSM 7.0.3 Approval Server
Do you also have these people set up with a change permission - Change Submitter Read license or ?? If Not, that might be the problem. :) Candace -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Chowdhury, Tauf Sent: Thursday, January 22, 2009 8:29 AM To: arslist@ARSLIST.ORG Subject: Re: ITSM 7.0.3 Approval Server David, Our forms are out of the box as well as the workflow. Tauf Chowdhury Analyst, Service Management Office: 631.858.7765 Mobile:646.483.2779 -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Easter, David Sent: Thursday, January 22, 2009 11:19 AM To: arslist@ARSLIST.ORG Subject: Re: ITSM 7.0.3 Approval Server That's generally true, James - but there is special code within AR System and ITSM that mitigates that requirement when using an ITSM out-of-the-box application. ITSM users do not need a write license to use approval server - a business benefit of using the BMC ITSM suite. However, your statement is correct for any non-ITSM (e.g. custom or home-grown) applications. In those cases, a write license is required for approval due to the section you pasted below. For the OP, the most common occurrence of this situation is when the original ITSM form is copied rather than modified or a new form is added. In other words, were you to create a new approval form, it may not be licensed properly as an ITSM application form. If that were the case, the special condition of the form being an out-of-the-box ITSM application form wouldn't be in force and the system would therefore require a write license to approve. So the first thing I would suggest would be to see whether that form is OOTB or whether it is a custom form or copy of the original. -David J. Easter Sr. Product Manager, Solution Strategy and Development BMC Software, Inc. The opinions, statements, and/or suggested courses of action expressed in this E-mail do not necessarily reflect those of BMC Software, Inc. My voluntary participation in this forum is not intended to convey a role as a spokesperson, liaison or public relations representative for BMC Software, Inc. -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of jham36 Sent: Thursday, January 22, 2009 8:09 AM To: arslist@ARSLIST.ORG Subject: Re: ITSM 7.0.3 Approval Server In order to approve a change you will need to have a fixed or floating license. Read licenses only let you submit and modify only the entries that you have submitted. I do not think that this applies here. >From the documentation: Within their assigned permissions, users with Read licenses can search for requests and display requests. In addition, administrators can configure the AR System server to enable users with Read licenses to do the following tasks: Submit requests Modify requests that they submitted The ability to allow those with Read licenses to submit requests allows you to reserve write licenses for users who need to modify requests that they did not submit. James On Jan 22, 10:49 am, "Chowdhury, Tauf" wrote: > Hi everyone. Here's the issue. > > In our Change process, we have business users (end users with read > license) who need to approve a change request. > > They should be able to go into the Approval Central and approve the > request when they view the change and it displays the > CHG:ChangeAPDetailSignature form. > > We do not allow guest users and all of our end users have a people > record with a READ license. > > However, they get this error when they try to approve: > > You do not have write license (ARERR 8932) You do not have write > access to field : > Password (ARERR 330) > You do not have write license (ARERR 8932) You do not have write > access to field : > User ID (ARERR 330) > You do not have write license (ARERR 8932) You do not have write > access to field : > Individual/Group (ARERR 330) > You do not have write license (ARERR 8932) You do not have write > access to field : > Approval Status (ARERR 330) > You do not have write license (ARERR 8932) You do not have write > access to field : > zTempAuthPassword (ARERR 330) > You do not have write license (ARERR 8932) You do not have write > access to field : > z1D Impact Area Required (ARERR 330) > You do not have write license (ARERR 8932) You do not have write > access to field : > z1D CHG Rules ID (ARERR 330) > You do not have write license (ARERR 8932) You do not have write > access to field : > zTmpPassword (ARERR 330) > You do not have write license (ARERR 8932) You do not have write > access to field : > z1D Char05 (ARERR 330) > You do not have write license (ARERR 8932) You do not have wr
Re: ITSM 7.0.3 Approval Server
David, Our forms are out of the box as well as the workflow. Tauf Chowdhury Analyst, Service Management Office: 631.858.7765 Mobile:646.483.2779 -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Easter, David Sent: Thursday, January 22, 2009 11:19 AM To: arslist@ARSLIST.ORG Subject: Re: ITSM 7.0.3 Approval Server That's generally true, James - but there is special code within AR System and ITSM that mitigates that requirement when using an ITSM out-of-the-box application. ITSM users do not need a write license to use approval server - a business benefit of using the BMC ITSM suite. However, your statement is correct for any non-ITSM (e.g. custom or home-grown) applications. In those cases, a write license is required for approval due to the section you pasted below. For the OP, the most common occurrence of this situation is when the original ITSM form is copied rather than modified or a new form is added. In other words, were you to create a new approval form, it may not be licensed properly as an ITSM application form. If that were the case, the special condition of the form being an out-of-the-box ITSM application form wouldn't be in force and the system would therefore require a write license to approve. So the first thing I would suggest would be to see whether that form is OOTB or whether it is a custom form or copy of the original. -David J. Easter Sr. Product Manager, Solution Strategy and Development BMC Software, Inc. The opinions, statements, and/or suggested courses of action expressed in this E-mail do not necessarily reflect those of BMC Software, Inc. My voluntary participation in this forum is not intended to convey a role as a spokesperson, liaison or public relations representative for BMC Software, Inc. -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of jham36 Sent: Thursday, January 22, 2009 8:09 AM To: arslist@ARSLIST.ORG Subject: Re: ITSM 7.0.3 Approval Server In order to approve a change you will need to have a fixed or floating license. Read licenses only let you submit and modify only the entries that you have submitted. I do not think that this applies here. >From the documentation: Within their assigned permissions, users with Read licenses can search for requests and display requests. In addition, administrators can configure the AR System server to enable users with Read licenses to do the following tasks: Submit requests Modify requests that they submitted The ability to allow those with Read licenses to submit requests allows you to reserve write licenses for users who need to modify requests that they did not submit. James On Jan 22, 10:49 am, "Chowdhury, Tauf" wrote: > Hi everyone. Here's the issue. > > In our Change process, we have business users (end users with read > license) who need to approve a change request. > > They should be able to go into the Approval Central and approve the > request when they view the change and it displays the > CHG:ChangeAPDetailSignature form. > > We do not allow guest users and all of our end users have a people > record with a READ license. > > However, they get this error when they try to approve: > > You do not have write license (ARERR 8932) You do not have write > access to field : > Password (ARERR 330) > You do not have write license (ARERR 8932) You do not have write > access to field : > User ID (ARERR 330) > You do not have write license (ARERR 8932) You do not have write > access to field : > Individual/Group (ARERR 330) > You do not have write license (ARERR 8932) You do not have write > access to field : > Approval Status (ARERR 330) > You do not have write license (ARERR 8932) You do not have write > access to field : > zTempAuthPassword (ARERR 330) > You do not have write license (ARERR 8932) You do not have write > access to field : > z1D Impact Area Required (ARERR 330) > You do not have write license (ARERR 8932) You do not have write > access to field : > z1D CHG Rules ID (ARERR 330) > You do not have write license (ARERR 8932) You do not have write > access to field : > zTmpPassword (ARERR 330) > You do not have write license (ARERR 8932) You do not have write > access to field : > z1D Char05 (ARERR 330) > You do not have write license (ARERR 8932) You do not have write > access to field : > z1D Integer01 (ARERR 330) > > I checked fields and Public is visible. > > I guess I want to have the same functionality as when an end user goes > into the requester console to submit a request. They can have a read > license but still type in notes. > > Any ideas? Thanks a lot. > > Tauf Chowdhury | Forest Laboratories, Inc. >
Re: ITSM 7.0.3 Approval Server
That's generally true, James - but there is special code within AR System and ITSM that mitigates that requirement when using an ITSM out-of-the-box application. ITSM users do not need a write license to use approval server - a business benefit of using the BMC ITSM suite. However, your statement is correct for any non-ITSM (e.g. custom or home-grown) applications. In those cases, a write license is required for approval due to the section you pasted below. For the OP, the most common occurrence of this situation is when the original ITSM form is copied rather than modified or a new form is added. In other words, were you to create a new approval form, it may not be licensed properly as an ITSM application form. If that were the case, the special condition of the form being an out-of-the-box ITSM application form wouldn't be in force and the system would therefore require a write license to approve. So the first thing I would suggest would be to see whether that form is OOTB or whether it is a custom form or copy of the original. -David J. Easter Sr. Product Manager, Solution Strategy and Development BMC Software, Inc. The opinions, statements, and/or suggested courses of action expressed in this E-mail do not necessarily reflect those of BMC Software, Inc. My voluntary participation in this forum is not intended to convey a role as a spokesperson, liaison or public relations representative for BMC Software, Inc. -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of jham36 Sent: Thursday, January 22, 2009 8:09 AM To: arslist@ARSLIST.ORG Subject: Re: ITSM 7.0.3 Approval Server In order to approve a change you will need to have a fixed or floating license. Read licenses only let you submit and modify only the entries that you have submitted. I do not think that this applies here. >From the documentation: Within their assigned permissions, users with Read licenses can search for requests and display requests. In addition, administrators can configure the AR System server to enable users with Read licenses to do the following tasks: Submit requests Modify requests that they submitted The ability to allow those with Read licenses to submit requests allows you to reserve write licenses for users who need to modify requests that they did not submit. James On Jan 22, 10:49 am, "Chowdhury, Tauf" wrote: > Hi everyone. Here's the issue. > > In our Change process, we have business users (end users with read > license) who need to approve a change request. > > They should be able to go into the Approval Central and approve the > request when they view the change and it displays the > CHG:ChangeAPDetailSignature form. > > We do not allow guest users and all of our end users have a people > record with a READ license. > > However, they get this error when they try to approve: > > You do not have write license (ARERR 8932) You do not have write > access to field : > Password (ARERR 330) > You do not have write license (ARERR 8932) You do not have write > access to field : > User ID (ARERR 330) > You do not have write license (ARERR 8932) You do not have write > access to field : > Individual/Group (ARERR 330) > You do not have write license (ARERR 8932) You do not have write > access to field : > Approval Status (ARERR 330) > You do not have write license (ARERR 8932) You do not have write > access to field : > zTempAuthPassword (ARERR 330) > You do not have write license (ARERR 8932) You do not have write > access to field : > z1D Impact Area Required (ARERR 330) > You do not have write license (ARERR 8932) You do not have write > access to field : > z1D CHG Rules ID (ARERR 330) > You do not have write license (ARERR 8932) You do not have write > access to field : > zTmpPassword (ARERR 330) > You do not have write license (ARERR 8932) You do not have write > access to field : > z1D Char05 (ARERR 330) > You do not have write license (ARERR 8932) You do not have write > access to field : > z1D Integer01 (ARERR 330) > > I checked fields and Public is visible. > > I guess I want to have the same functionality as when an end user goes > into the requester console to submit a request. They can have a read > license but still type in notes. > > Any ideas? Thanks a lot. > > Tauf Chowdhury | Forest Laboratories, Inc. > > Analyst, Service Management > > Informatics-Infrastructure > > Office: 631.858.7765 > > Mobile:646.483.2779 > > ** > This e-mail and its attachments may contain Forest Laboratories, Inc. > proprietary information that is privileged, confidential or subject to > copyright belonging
Re: ITSM 7.0.3 Approval Server
In order to approve a change you will need to have a fixed or floating license. Read licenses only let you submit and modify only the entries that you have submitted. I do not think that this applies here. >From the documentation: Within their assigned permissions, users with Read licenses can search for requests and display requests. In addition, administrators can configure the AR System server to enable users with Read licenses to do the following tasks: Submit requests Modify requests that they submitted The ability to allow those with Read licenses to submit requests allows you to reserve write licenses for users who need to modify requests that they did not submit. James On Jan 22, 10:49 am, "Chowdhury, Tauf" wrote: > Hi everyone. Here's the issue. > > In our Change process, we have business users (end users with read > license) who need to approve a change request. > > They should be able to go into the Approval Central and approve the > request when they view the change and it displays the > CHG:ChangeAPDetailSignature form. > > We do not allow guest users and all of our end users have a people > record with a READ license. > > However, they get this error when they try to approve: > > You do not have write license (ARERR 8932) > You do not have write access to field : > Password (ARERR 330) > You do not have write license (ARERR 8932) > You do not have write access to field : > User ID (ARERR 330) > You do not have write license (ARERR 8932) > You do not have write access to field : > Individual/Group (ARERR 330) > You do not have write license (ARERR 8932) > You do not have write access to field : > Approval Status (ARERR 330) > You do not have write license (ARERR 8932) > You do not have write access to field : > zTempAuthPassword (ARERR 330) > You do not have write license (ARERR 8932) > You do not have write access to field : > z1D Impact Area Required (ARERR 330) > You do not have write license (ARERR 8932) > You do not have write access to field : > z1D CHG Rules ID (ARERR 330) > You do not have write license (ARERR 8932) > You do not have write access to field : > zTmpPassword (ARERR 330) > You do not have write license (ARERR 8932) > You do not have write access to field : > z1D Char05 (ARERR 330) > You do not have write license (ARERR 8932) > You do not have write access to field : > z1D Integer01 (ARERR 330) > > I checked fields and Public is visible. > > I guess I want to have the same functionality as when an end user goes > into the requester console to submit a request. They can have a read > license but still type in notes. > > Any ideas? Thanks a lot. > > Tauf Chowdhury | Forest Laboratories, Inc. > > Analyst, Service Management > > Informatics-Infrastructure > > Office: 631.858.7765 > > Mobile:646.483.2779 > > ** > This e-mail and its attachments may contain Forest Laboratories, Inc. > proprietary information that is privileged, confidential or subject to > copyright belonging to Forest Laboratories, Inc. This e-mail is intended > solely for the use of the individual or entity to which it is addressed. If > you are not the intended recipient of this e-mail, or the employee or agent > responsible for delivering this e-mail to the intended recipient, you are > hereby notified that any dissemination, distribution, copying or action taken > in relation to the contents of and attachments to this e-mail is strictly > prohibited and may be unlawful. If you have received this e-mail in error, > please notify the sender immediately and permanently delete the original and > any copy of this e-mail and any printout. > > ___ > UNSUBSCRIBE or access ARSlist Archives atwww.arslist.org > Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are" ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are"
