New Organization Manager in Jamio 4.8

Organization modeling will be performed in the same way, but with a different tool that's even more business-friendly: there's no need to install any software, as management can be done through any browser on any operating system. The objects represented remain the same, and where a published , it can be viewed and edited.

We wanted to evolve the tool towards a correct positioning of the concepts: it is correct that a solution is represented at design time (abstracting from the concreteness of a specific organization) with a specific tool ( Jamio Composer ), while the organization , specific to the subject where the solution must function, is instead modeled at run time ( Admin Console ).

Alias ​​and group management allows you to combine an abstracted solution modeled to work with any organization with a specific organization represented at runtime in a cloud workspace.

Users will continue to use the solutions without any impact . However, it will be possible to assign permissions to certain users in the organization to view the organizational structure in a graphical view, and also to assign permissions to certain "specific" users to modify the organizational structure. Until the previous version, the graphical view of the organizational structure and its modification could only be done in Jamio Composer.

Jamio designers can focus on modeling the solution without the burden of defining and maintaining an organizational structure. This gives them greater freedom to build universal solutions that can work in any organization. This allows for a more flexible approach to defining access and responsibility rules and simplifies ACL definition.

Admin Console 's design tools . All modeling takes place in a so-called working copy . Until the working copy is published, it can be edited by all authorized users and is not available in the Jamio area. Editing on a working copy can be delegated from one user to another. Only one user can edit it at a time.

When this working copy is published , it is available in the workspace. To make further changes, you need to move the organization to a new working copy. This restarts the editing cycle, and the last published version remains available in the workspace until the next publication.

In this version 4.8, these remain unchanged; in the next version (4.8 R1), account management, account policies, and password policies will also move to the Admin Console , followed by the other administrative functions. The Admin Console already allows you to view the list of created accounts and manage their disabling.

Yes, everything stays as it is.

His task will be made easier: if until the previous version he was forced to use Jamio Composer only to manage the organization (which he edited and then published), he will continue to do the same thing with the full web editor available in the Admin Console, in addition to the fact that he will be able to delegate this task to others who do not have the administrator role.

When I open that solution with the new Jamio Composer, I'll no longer see the organizational component. The aliases that reconcile organizational elements must therefore be updated. The upgrade does its best to automate the transition, but there may still be some things that need to be fixed manually.

Yes, template customizations are always done in the design environment ( Jamio Composer ), while the associations of these templates to organizational elements are done in the organization editor ( Admin Console ).

I do this in the organization editor ( Admin Console ), by accessing the single entity and selecting the available templates.

The platform manages it at the time of publication.

Yes, absolutely. The Admin Console will display and manage all the organizations in your workspace, and you can create a new organization at any time.

An organizational chart can be exported to a file and then imported into another workspace.

ACLs have been separated, there are ACLs related to the organizational structure, manageable from the Admin Console, and ACLs related to custom templates.

In fact, the ACLs for exploring organizational structure , modifying organizational structure , and assigning tasks from Jamio Composer and are transferred to the Admin Console . For existing solutions, these ACLs will be found directly in the new environment.

Organization Managers, is defined Only members of this group can publish new organizational structure templates.

Adminsitrator user belongs to this group.

If the built-in template is used to create tasks from Jamio on Stage, this operation can be performed by anyone belonging to the Organization Manager group, and therefore by default only by Administrators.

If you are using a custom template instead, you need to define ACLs from Jamio Composer for the usual CRUD permissions on the template (specifically “create”) and also assign the permission to create tasks from the Admin Console .

While editing a working copy, there's an undo that allows you to cancel everything and start over. However, if I've published a template with errors and want to revert, I have to retrieve a previous version and republish it.

There is currently no feature to show previous versions of an org chart (this will be developed in a future release) so I need to have a previous export to retrieve.

In any case, all published versions are archived, so recovery is always possible through Openwork customer service.

A CSV format has been defined that allows any organization represented in that format to be imported into Jamio.

Of course, the drawing can be exported in SVG format.