Hi Nikhil,

Agree with what Carlos said. No need for any custom development as it can be done from Java client configurations itself. See below example pic. You have to do similar kind of update as per your requirement:

Hi Nikhil,

If you’re using Groovy, then yes, you have to throw DSLException to stop the promotion of workflow status if a condition is not satisfied or some error happens and propagate the message to users. There’s no other way than throwing the exception.

Hi Matt,

For some strange unknown reason am unable to post the actual answer. Hence am pasting a screenshot of it. Please check & let me know if it helps.

Hello,

There is no easy way to do it. However, I can suggest two alternative workarounds.

1. Select Print option from Action Menu dropdown of that particular item. Select All Tabs and below that All Levels for BOM option. Now when you click on Preview or Print, a web page will be generated showing a BOM Explosion along with Pending Changes info. You can save it as a PDF.

2. Export the item from Action Menu options creating a custom filter with Changes & all BOM levels. The output you get will be in Excel format.

Hi Mahign,

Your query is not fully clear to me. However, based on my understanding, below is a sample code to get the next autonumber of a Part which is in the affected items of a ECO. Similar thing can be done for Relationships tab also. Here my sample ECO contained only one row so I haven’t iterated over the table in a loop.

<br />String next = "";<br />IChange change = (IChange)session.getObject(IChange.OBJECT_TYPE, "C00004");<br /> IItem item = (IItem) change.getTable(ChangeConstants.TABLE_AFFECTEDITEMS).getReferentIterator().next();<br /> for(IAutoNumber an : item.getAgileClass().getAutoNumberSources()){<br />        next = an.getNextNumber();<br /> }<br />Map&lt;Integer, String&gt; attributes = new HashMap&lt;Integer, String&gt;();<br /> attributes.put(ItemConstants.ATT_TITLE_BLOCK_NUMBER, next);<br /> session.createObject(IItem.OBJECT_TYPE, attributes);<br />

select * from scheduled_event_tracking;

It can be done more easily with this query:

select item_number from item where default_change = 0 and latest_released_eco = 0;

Please ensure you have Manage Global Views in the right hand pane of the Applied To section of the Administrator privilege. This should resolve your issue.

Hi Kevin,

Not sure if your problem has been already resolved or not. If not, then have you tried setting the log4j config file in Agile’s start up script?

If you have access to agile schema, connect with agile user & run this query:

select delete_flag from item where item_number = ‘AS72613’;

If it returns zero rows, that means the item has been hard deleted. If the delete_flag is set to 1, it means it’s in soft deleted state but sometimes in doesn’t show up in the recycle bin. Set it to 0 to make it visible by search again.