Why not create a custom Web Service which should be fairly easier and
quicker ?

Thanks
Mahesh

On Thu, Aug 5, 2010 at 1:20 PM, sayana dixit <sayanadi...@gmail.com> wrote:

> **
> Thanks for the reply,
>
>  Here is what i understood..
>
>  Right now we have two option..if we go for upgrade from 7.5 to 7.6 ,
> atleast we can get the corporate ID field
> available on published web services, but the second part of populating
> first and last name is still remaining and need to get it done by some cusom
> work flow.
>
> If we  remain on 7.5 and still want to achieve the solution then need to
> develop both requirement
> 1) make corporate ID available
> 2) create custom workflow to populate first and last name.
>
> Regards
> Sayana.
>
>
>
> On Thu, Aug 5, 2010 at 10:18 AM, strauss <stra...@unt.edu> wrote:
>
>> **
>>
>> Don’t know why, but I agree; I’m in the middle of brain surgery on the 7.6
>> CTM:PPS:Search workflow to add Login_ID everywhere (and remove my
>> customizations for Corporate ID that are now redundant), and I’ll try to see
>> if it can be done.
>>
>>
>>
>> Christopher Strauss, Ph.D.
>> Call Tracking Administration Manager
>> University of North Texas Computing & IT Center
>> http://itsm.unt.edu/
>>
>> *From:* Action Request System discussion list(ARSList) [mailto:
>> arsl...@arslist.org] *On Behalf Of *Mahesh
>> *Sent:* Thursday, August 05, 2010 12:13 PM
>> *To:* arslist@ARSLIST.ORG
>> *Subject:* Re: modifying OOTB incident create Web Service
>>
>>
>>
>> **
>>
>> Another thing that may not be directly related to this subject is the
>> Search criteria or various forms.
>>
>>
>>
>> For example, on the Incident we can search for a person based on Last
>> Name, Corporate ID, Email but not Login ID and then it retrieves everyone
>> ignoring the People "Profile Status".
>>
>>
>>
>> I think it should retrieve People only with a profile status of "Enabled".
>>
>>
>>
>>
>> Thanks
>>
>> Mahesh
>>
>> On Thu, Aug 5, 2010 at 11:02 AM, strauss <stra...@unt.edu> wrote:
>>
>> **
>>
>> Use Corporate ID for the Empl serial number (that is what it is for).  In
>> ITSM 7.6 they _*finally*_ added Corporate ID throughout the application
>> as an identifying value for customers, which may lessen your concerns that
>> First and Last are required – again, throughout the applications.  You may
>> want to add a custom filter to populate First and Last after you supply
>> Corporate ID to the HPD_IncidentInterface_Create_WS, but I cannot say if
>> that is necessary since we do not use the web services.  Otherwise you may
>> have to disable the workflow that traps for missing First and Last values
>> while an Incident is being created.
>>
>>
>>
>> Unfortunately they still have not added Login_ID (in 7.6), which is what
>> we have to use for _*everything*_ where customer records are concerned;
>> we continue to have to customize the apps, but at least Corporate ID is no
>> longer a part of that customization like it was in ITSM 7.0.0x.
>>
>>
>>
>> Christopher Strauss, Ph.D.
>> Call Tracking Administration Manager
>> University of North Texas Computing & IT Center
>> http://itsm.unt.edu/
>>
>> *From:* Action Request System discussion list(ARSList) [mailto:
>> arsl...@arslist.org] *On Behalf Of *sayana dixit
>> *Sent:* Thursday, August 05, 2010 10:43 AM
>> *To:* arslist@ARSLIST.ORG
>> *Subject:* modifying OOTB incident create Web Service
>>
>>
>>
>> **
>>
>> Hi all,
>>
>>
>>
>> I have a requirement to modify the HPD_IncidentInterface_Create_WS in such
>> a way that First name and Last name should no more be a required field,
>> rather
>>
>> there should be a new field on the WSDL called Empl serial number and that
>> should be a required field. Also , i need to create a workflow which would
>> populae
>>
>> the first name and last name on HPD:Incidentinterface_Create form using
>> Empl serial num(from web service) and thus creating the incident ticket.
>>
>>
>>
>> Any ideas /thoughts on this, please share..
>>
>>
>>
>> Regards
>>
>> Sayana
>>
>>
>>
>> _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_
>>
>> _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_
>>
>>
>> _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_
>>  _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_
>>
>
> _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_
>

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

Reply via email to