​@Evelien , ​@Marjolein Verstraten could you shed a light on this one?

Hello ​@Ricky,

I can try to shed some light on this, however, I might need some additional context if my answer falls short.

These requests have to be rewritten using the Resource Staging | Thinkwise Documentation mechanism to comply with Indicium.

With regard to this, your requests on Indicium Basic should also work on Indicium Universal. It is not the case that resource staging is mandatory. Sending one request with a JSON body with all column values in it, as you did on Indicium Basic, can also work on Indicium. This is explained here. There are a couple of differences between this ‘Single request resource staging’ and the Indicium Basic API, most notably:

• Column-level permissions - Indicium Basic does not support column level permissions so if you supply any unauthorized columns, Indicium will reject your request after transitioning.
• Default and layout - Indicium will handle the provided columns in order and perform default and layout procedures after each one (as if you were entering a form yourself). If a layout procedure marks the next column in the request as hidden or readonly, Indicium will reject your request. Since defaults are also performed after each column, the inserted/updated values might be different depending on your default logic.

Whether or not you should want or need to switch to resource staging depends on your goal and any problems you foresee with keeping the requests as they are. I would recommend reading through section 5 which I linked and determine if you can keep your requests as is.

We are wondering if and what will change overtime and on the short term in this mechanism to make sure the Windows GUI will function the way it currently works: Will the Indicium way of talking change, will it be only the Windows GUI that will be altered to speak the Indicium language/mechanism or will both be changing maybe?

As it stands, no notable changes will be made to the Indicium API in order to facilitate the Windows GUI. We take great care when designing the Indicium API to account for possible futures and avoid needing to resort to breaking changes when these happen. The Indicium API was always designed with the possibility that the Windows GUI could be connected to it in mind. With that said, the needs of the Universal GUI and the Windows GUI are nearly identical, as both aim to offer the same feature set. On top of that, when we do make changes, we always try to keep backward compatibility in mind and avoid breaking changes, as this is in everyone’s best interest, including ours.

I do foresee the possibility that the import API may undergo some changes in the future in order to offer a better import experience. However this is not something I can say with certainty, nor do I have any details on what this might look like at the moment. If this ends up happening, we will try to avoid/minimize breaking changes and communicate those that do occur in the release notes.

I hope this clarifies some things.