# Kirona
### Launching Keyfax
These are the launch and test Keyfax steps with Kirona Job Manager integrated with Keyfax Repairs Diagnostics.
1. Launch Job Manager: Username: KEYFAX01, Password: password1
2. Choose to create a Job (from the Create menu on the Left Hand side)
3. When prompted for what type of job choose Works Management Case (WM Case):
4. Confirm WM case is the integration by looking at the “About” drop down. You can also check that the URL is correct for launching Keyfax:
5. To Launch Keyfax, an asset (property) that YHN actually maintains must be chosen from the list of all properties. So a postcode search can be made (e.g. for NE6 3…) and then select a “Managed Property” (maintained by YHN), and click on “Add Selected Item”, which adds it to the WM Case.
6. At this point the Keyfax button becomes fully blue and clickable:
### Known Errors
When initially set up as intended as above Kirona JM gave an error:
This was due to being logged into JM as a user “ADMIN” not known in Keyfax. Once set up (KEYFAX01) this worked fine (Jake actually logged in as another user). However, as part of the integration Kirona have decided to hardcode the user as “operator” with an incremented number to set up a unique OrderID. From the database orders:
Previous to this, Keyfax wouldn’t launch under https with a wildcard certificate if (as was set by default) TLS1.3 Client was switched on in the Win 2019 registry. Once switched off Keyfax worked fine. So on this KEYDCB002 server we have restricted TLS to be 1.2 only.
