Hi Rick,

 

Perhaps I've misunderstood your issue, but if not it could be a simple
oversight.  Presumably you are doing the push to AST:BulkInventory?  If so,
simply pre-set the GUID with Application-Generate-Guid and then your
workflow will have "captured" it J  

 

Cheers

 


Ben Chernys
Senior Software Architect
logoSthInc-sm  

Canada / Deutschland
Mobile:      +49 171 380 2329    GMT + 1 + [ DST ]
Email:       Ben.Chernys_AT_softwaretoolhouse.com
Web:          <http://www.softwaretoolhouse.com/> www.softwaretoolhouse.com

We are a BMC Technology Alliance Partner

 

 

Check out Software Tool House's free Diary Editor and our  Freebies Section
for ITSM Forms and Fields spreadsheet.

Meta-Update, our premium ARS Data tool, lets you automate your imports,
migrations, in no time at all, without programming, without staging forms,
without merge workflow. 

 

Meta-Archive does ITSM Archiving your way: with your forms and your
multi-tenant rules, treating each root request as the tree of data and forms
that it is it is.

 

Pre ITSM 7.6.04?  Clarify?  Roll your own?  No problem!

You can keep your valuable data!


 <http://www.softwaretoolhouse.com/> http://www.softwaretoolhouse.com/  

 

 

 

 

 

From: Action Request System discussion list(ARSList)
[mailto:[email protected]] On Behalf Of Rick Westbrock
Sent: July-10-14 21:57
To: [email protected]
Subject: How can I capture the instance ID of a newly created asset?

 

** 

Hi all-

 

I am still on my ARS 7.1/ITSM 7.0.03 system. I have a custom
shipping/receiving module where we have a regular form that is used to
interact with the CMDB. A few months ago I deployed new code which is able
to take an asset that is In Inventory and change it to Deployed status,
remove the location relationship and relate it to a person. My new challenge
has been to use the regular form to receive both existing assets and new
assets.

 

I didn't have too much trouble building the workflow to receive back an
existing asset and update the status to In Inventory and create all the
required relationships. I have also been able to receive in a new asset and
create a new record in the appropriate AST form (based on the class of the
product catalog entry) but I just can't seem to properly create a new asset
for a bulk inventory item. The part I am struggling with is getting the push
fields to the BMC.COR:BMC_Dependency and AST:InventoryQuantity forms because
I haven't been able to capture the Instance ID of the new record in the
AST:BulkInventory form.

 

I was able to leverage the existing CMDB workflow but those problem push
fields actions are performed by active links in the GUI and I just can't get
it to translate to filters. I tried using the $LASTID$ to do a set fields
from AST:BulkInventory in the action immediately after the push fields to
that form but there are lots of BMC filters that fire in the interim so I'm
not getting the expected value back for that keyword.

 

Does anybody have any suggestions for how to attack this problem? The only
other thing that I have come up with is not desirable at all: doing a set
fields from AST:BulkInventory based on timestamp (created in the last 3
seconds for example) which is extremely ugly but might work in our
environment for now since there's not much activity. The caveat is that the
next phase of the project will be to build out batch receiving where the
user can upload a CSV file with potentially multiple bulk inventory assets
to be created so the timestamp method will break in that scenario.

 

 

Thanks in advance,

Rick

_________________________

Rick Westbrock
Remedy Administrator | IT Department
24 Hour Fitness USA, Inc.

 

No virus found in this message.
Checked by AVG - www.avg.com
Version: 2013.0.3485 / Virus Database: 3955/7831 - Release Date: 07/10/14

_ARSlist: "Where the Answers Are" and have been for 20 years_ 


_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to