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; } } }

DAS - Error trapping

Mr_Cruise

OS - Soalaris
TS - 6.5
OD - 6.0.2
DB - Oracle

Dear All,

I have configured DAS to save a DCR type to a table which is all working fine. The only concern I have is that if DAS fails, for whatever reason, there is no way of informing the user.

I was thinking of maybe writing a call server method, that would be invoked after save, to go and check that the record/s had indeed been inserted/updated.

Does anyone have any better ideas?

Thanks in advance.

Lee

Find more posts tagged with

Comments

Mr_Cruise

Another option is to switch to use stand-alone deployments and use a callserver to invoke the deployment. However, if this fails the DCR has been saved and there is nothing stopping that DCR from being submitted.

The most complete but complex solution would be to change the whole flow to; when save is clicked the call server is called and passed all the data. The DCR would only be saved, by calling the real save event, if the DCR was saved to the database.

Any ideas/views?

Sailesh

Another option is to switch to use stand-alone deployments and use a callserver to invoke the deployment. However, if this fails the DCR has been saved and there is nothing stopping that DCR from being submitted.

The most complete but complex solution would be to change the whole flow to; when save is clicked the call server is called and passed all the data. The DCR would only be saved, by calling the real save event, if the DCR was saved to the database.

Any ideas/views?

Using a call server sounds a better solution, specially since it is whole solution, you can warn the user the DD is down so update won't get reflected into database.