Packaging observation post 6.8 P4 Upgrade
I was wondering whether anyone else has observed some irregularities when it comes to installing Archer packages...
For the most part the packaging process performs as it should, however we have noticed that a number of application also be updated...well more like the last updated timestamp is the same as the timestamp associated on the recently intended packaged application.
It seems that random applications would be affected in this way, in all cases the affected application has not been changed in anyway, let alone be available within the package as application to be installed/updated.
It is an odd one, we think it may be related to another issue we experienced regarding our subscription notifications not triggering. At the time we noticed that the notifications had been "updated" with the same time as a recently package install.
The resolution for that was to update the default letterhead we're using; the Archer support team is aware of the notification issue. And to be honest we may go back to them regarding the packaging observation, just thought to ask and see if anyone else has experienced anything similar.
Thanks for your time,
- 6.8 p4
- archer packaging
- Community Thread
- Forum Thread
- install packages
- RSA Archer
- RSA Archer Suite
David, for the most part it would seem that the cross reference applications are being affected. I just perform a package install not so long ago from our DEV to TEST environment and I can see the timestamp of the cross reference applications subscription notifications have been updated along with subscription notifications that are associated with applications and questionnaires that have not been cross referenced within the application I packaged/updated.
We are currently testing our 6.8 P4 HF2 archer version, Jason Taylor the issue with sub. notifications not triggering, is it due to the xref fields linked with sub. notification applications included in the packages which were being installed?
I've experienced intermittent issues with Digest style notifications in 6.8P2. Resaving the notification object generally prompted it back to life. The Letterheads also required a resave post upgrade to that version. After ever package we guage the success of digest notifications on the first cycle post package up hoping it doesn't break again (Resaving every record isn't always viable, after every package install..). Have also noticed that sometimes some of the calcs stall alos, and require a save to refresh, or potentially a calc order change.