Users; Full Importing and Exporting of Users now available

User Import

An Import action has been added to the form "Tools, User Security, Users" under "Utilities". This action will import the User record from an XML file.

This Import Action behaves slightly differently from other finPOWER Connect forms. If the Imported User already exists and you choose to override the existing User, then the User form behaves like other forms - the fields will be populated and the form will be switched to Edit mode.

However, if the Imported User does not exist in the Database or you select "No" when prompted "Would you like to update this User?". Then the User will be imported and saved immediately without entering into edit mode. This is due to there being two different forms for new Users and existing Users. Due to system limitations, it is impractical to open the new User form from the Import Action.

Note that if the User exists, and you choose "no" when prompted "Would you like to update this User?". The System will attempt to generate a new User Id based on the one being Imported. For instance, if Importing a User with Id "Guest" which already exists in the Database, then the new id could be "Guest1".

Additionally, a new function has been added to finUser called FromXmlString. This function reads an XML String into a finUser object. The FromXmlString function has four parameters:

• xml [string]
• The XML to be parsed.
• updateExisting [boolean], default false
• If true, existing records will be updated. If false the process will fail if a user exists with the same UserId.
• ignoreForeignPks [boolean], default false
• If true, pks in the XML will be ignored and the given Record Id will be used instead. If false, it will attempt to use the given pk and will fall back to the Id should it fail.
• warnings [finWarnings] Optional, default Nothing
• Any Warnings that occur during the Import Process will be returned via this parameter.

User Export

An Export action has been added to the form "Tools, User Security, Users" under "Utilities". This action will export the User record to an XML file.

Additionally, a new function has been added to finUser called ToXmlString. This function converts the finUser object into a XML String representation. The ToXmlString function has two Optional Parameters:

• includeXmlHeader [boolean], default False
• If true the XML metadata header is included.
• prettify [boolean], default True
• If true the XML will be formatted to be more readable.

Import/ Export Information

Previously, Users could not be "fully" Imported and Exported. The File, Import/ Export Information, Export Information form has an option for "Users & Responsibilities". However, this would only Export the User Extended Data and could not be used to re-import the User.

The Export Information form has been updated to fully export a User. Likewise, the Import Information form has been updated to allow Users to be imported.

When Exporting, you can select which Users to include by using the "Users & Responsibilities" lookup on the Parameters Page. If this is left empty or if you enter "*", then all Users will be included in the Export.

The current User cannot be imported. This is to prevent the current user potentially locking themselves out when doing a bulk User import.

Cloud

In finPOWER Connect Cloud, Users can now be imported from the Users list view by going to Administrator, User Security, Users. This behaves the same way as the finPOWER Connect Desktop form.

Likewise, Users can now be exported in finPOWER Connect Cloud by drilling down to a User from the Users Grid. The Export button is available from the Actions menu. This will also behave the same way as the finPOWER Connect Desktop form.

Important Notes

• When a user is imported it will be set as inactive and "Force User to change Password" option will be set to true. Additionally, a strong password will be automatically set. This means that the imported user will not be able to login after an XML import takes place until an Administrator makes the User Active and sets a new password.
• It is recommended that User Groups and User Policies are also exported and imported when bulk exporting Users.