Re: How to rename halcust folders when updating versions
Kristaps Žogots
2-11-17
I will try to cover two cases: updating from Cloud Controller (applies only to partners who has a separate Cloud Controller) and updating from MyStandard page.

MyStandard:
At the current moment it's not possible to do halcust updates when updating version. You by default the server will keep the same halcust/halpatch for the new version. In coming weeks we will add option to upload halcust/halpatch just before update.

Cloud Controller:
1. In the server folder you need to create a folder newver.XXX, where XXX is the version code of the version you will update the server to. For example, newver.STDSVR_8.3-2017-01-08-0011
2. Put the new halcust and halpatch in the newly created folder.
3. In the remote cloud server record you need to set Halcust Update and Halpatch Update radio buttons to values "Use Updated"
4. Perform the server update function.
Leave Comment
You can subscribe to notifications for this post by selecting the 'star' icon on the top right corner of the post.
Latest Posts
Piotr Wycichowski
Thanks Gatis, anyway it seems to be reported as bug instead of wish because now it depends on who created task for whom, am I right? /Piotr W....
14:39 15 May 2024
Aldevinas Katkus
Actually a new version of this bug is SL>>Reports>>Periodic customer statement "accumulates" amounts Not sure why it was duplicated, I clicked "submit"only once....
08:09 10 May 2024