OptiPaaS shows a compact view where filters and file stat are collapsed.

Once expanded the OptiPaaS will remember the state.

Filters are frequently used, they are so preset automatically.

The whole idea of the ‘one click’ access to files, activity and alerts from anywhere on the system is based on presetting the filters.

The statistics give quick access to filtering including date ranges.

Filters are further used for the lists in the partner account.

The whole navigation through the system is based on the design that you can start anywhere – from files, transports or participant and move around quickly.

Another major design idea in the system is that ‘files’ are always in context of transport and org (origin).

It does not stand on its own. It has many benefits, and in effect replaces the folder based structure.

OptiPaaS is full of connected ideas.

The goal of OptiPaaS is to address the large scale problem of file exchange with many participants going through many transports.

One of the main problems with large scale solutions is to address fragmentation.

A transport is a ‘looking forward’ entity which was designed to accommodate new participants.

It is not a ‘job’ – it is a more like a ‘route’ or… a ‘transport’.


Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment