Brian Howard
One way to better understand how the system should work is to just show it for others to try. The posts below cover different features in O4. Give them a try and let us know what you think!
0
Comments
Please sign in to leave a comment.
This is a very quick overview of the project editor. If you don't see the edit button, then you need to setup your OASIS account to be "Full Access". This may take a bit to sync to the cloud. (Sometimes we have to reload the instance to affect user account. Just let us know if you have questions.
https://web2.oasissalessoftware.com/OASIS/VKB/O4/ProjectEditorOverview.mov
Thanks Brian! Once a layout is customized by the user, does that layout persist for other viewers of the project, and can the user reuse that layout on other projects or save it as a view?
Yes, they layout persists for other users. This is typical for OASIS and only the project editor. The use-case is that different quoters look at the world differently in many offices (distributor and rep). Usually a difference in business model (e.g. switchgear/lighting, project/stock etc.). Each needs to see the world differently, but the project needs to be seen as the previous person left the project. (Learned this one the hard way a long time ago.)
By the way - you might notice we are gearing up for multiple editors in the project at the same time. More on that later.
Biran, will the multiple editors also allow for multiple quoters to be listed on the project? For example a lighting quoter and a controls quoter?
Yes - and both will "see" each others changes.
We are having people do this right now and complaining about the "last save wins" reality. With the new technology, we can have the system merge the results in real time.
HOWEVER: they must be on the same database and that will be a support headache for us that we are trying to figure out. Essentially it will work if both are using O4 in a browser. However, if "the lighting guy" is working in V2.7 in the office (or even the O4 GUI) for max speed and the controls guy is using the browser, we are back to a last save wins scenario. Ugh ...
On Friday, I enabled Full Access for myself and a couple of other power users in the office. It looks like the property synced between user files, as it reads correctly in O4>Configuration>Users, however the option to edit doesn't show as expected per the video clip in this post. Is this a situation where the instance needs to be reloaded? If so, would it need to be reloaded every time a user is given a Full Access license (or a license is revoked), or is this is a short term situation while the bugs are worked out?
Looks like you are on a production server that does not have that code update just yet. That will change on Saturday (last least over the weekend).
We have BETA users that update pretty frequently and that can cause issues with people doing production work (not all, but some). JSON integrations can be negatively affected with the beta release schedule which can be daily.
Production O4 updates go out once a month - typically the Saturday after the first Tuesday of the month to coordinate with the GUI production update.