This implementation was replaced by Slave Instances implementation.

This part contains workflows modifications.

Threat Slave Instance as same as Software Instance in this case.

add tests to validate if a slave instance is stopped and started when a software instance is started and stopped

add steps to validate if a software instance user has access to view a sale order that is associated with one slave instance

add role to software instance user as Auditor to each Slave Instance installed in the same Computer Partition where the Software Instance is insta

refactor code to select the portal type. This refactoring is possible use this script to add role to Sale Orders associated to Slave Instances.

remove checkPermission because is not used and add the reference of each Slave Instance. The reference is used to generated the key to access it

This UI should be improved to make it looks nicer.

Refactor code to find correctly a Software Instance, because if slave_reference is None the query must ensure that Slave Instance will be ignored

Add step to check if the connection_xml of a Software Instance is changed correctlyAdd step to check if the connection_xml of Software Instance is changed correctly

This theme is really complex, and having beautiful buttons which are submitting
form is worse then just have working links without side effects.

remove flag to skip the test and add assert to validate if the connection_xml from Slave Instance was edited correctly

Add security tests to validate roles used access Slave Instances objects using Software Instance user

Add role to allow a Software Instance access and edit the Slave Instance installed in the same computer partition and software release.

Add script to allow a Software Instance access and edit the Slave Instance installed in the same computer partition and software release.

Add Auditor role to allow a software instance user access a Hosting Subscription related by one Slave Instance. So, when a Slave Instance and a software instance use the same computer partition and software release, the software instance user can access the Hosting Subscription.

Add Auditor role to allow a software instance user access a Sale Packing List with one Slave Instance. So, when a Slave Instance and a software instance use the same computer partition and software release, the software instance user can access the Sale Packing List with this Slave Instance.

It is important to cover a case when Software Release get archived, but it is
still used on Computer.