nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Setting Extended Attribute for DCR on save

acezone

Hi All,

I have never come across to situation where as I am curious to know if there is any possible way of setting an EA on saving a DCR.

Please do share your thoughts and views in this respect.

Regards,
Ace

Find more posts tagged with

Comments

Adam Stoller

Hi All,

I have never come across to situation where as I am curious to know if there is any possible way of setting an EA on saving a DCR.

Please do share your thoughts and views in this respect.

Regards,
Ace

Yes it's possible, but I'm not sure if it is really advisable.
Basically you have an onSaveDone event handler that does a callServer() which sets the EAs on the DCR - however, since this is asynchronous and happens after the save has been completed - what do you do if the setting of the EAs fails?
You could send an alert to the user - but the widow might not still be open so they won't see it. If they do see it - might it not be more confusing than helpful?
It would probably be better to do something like this as part of a workflow task.

Bjorn

Hi All,

I have never come across to situation where as I am curious to know if there is any possible way of setting an EA on saving a DCR.

Please do share your thoughts and views in this respect.

Regards,
Ace

Yes it's possible, but I'm not sure if it is really advisable.
Basically you have an onSaveDone event handler that does a callServer() which sets the EAs on the DCR - however, since this is asynchronous and happens after the save has been completed - what do you do if the setting of the EAs fails?
You could send an alert to the user - but the widow might not still be open so they won't see it. If they do see it - might it not be more confusing than helpful?
It would probably be better to do something like this as part of a workflow task.

I would read ghoti's post. The async issue he brings up involves using the FormAPI event registry to call a function onsavedone. This function would use the FormAPI method IWDatacapture.callserver().

If you're not using workflow as ghoti suggests or still want to have it done onsave for some other reason, you can get around the async issue he mentions by using your "own" XMLHttpRequest object or library instead of FormAPI's callserver() to make a synchronous call to server side code that sets the EA for you.

And for the sake of being proactive, if you need sample code using callserver() that you can adapt to meet your needs, search around the forums for existing code people have posted. I can also post a working example using the synchronous method I've described...for a medium-to-large fee.

I never understood why IW doesn't have an "async" option/param you can use like most browsers have with their implementation of the XmlHttpRequest object on the open() method. I am sure there is a good reason, but sometimes the potential pitfalls of using synchronous calls are worth risking.