NeilWJ

Hi @Paul Alexander, I will add it in. Cheers

Follow Up Information:- On upgrade any existing "active" captures will be automatically versioned to version 1. You will notice the versioned By is set to SYS_SYSTEM. Any captures that are in an "inactive" state at the time of upgrading will not be versioned because, well, they are inactive which mean they are in a "draft" state.

_

Hi All, The long awaited support for PCF versioning is now live. When your instance is updated during your server maintenance window it will automatically enable in the Administration tool. It works in the same way as BPM. The UI for publishing a PCF is practically the same. So now you will as normal edit the "draft" and when you want to release that draft you simply publish it. Again like BPM versioning you can de-activate/re-publish a specific version of your PCF. Cheers

Hello All, The PCF versioning work will be going live imminently. I believe a server build will go out tomorrow all being well. The admin tool that was released today has support for it and will automatically switch over when the instances get updated to next platform release. The versioning works just like the BPM, same sort of publishing form and you work on the draft and publish the draft when it is ready to go out etc. Cheers 7 FYI @Brhow @Martyn Houghton @AmyW @Alberto M @Carl Tovey @Alisha @Jeremy @HHH @Joanne @HGrigsby @Aaron Summers @Dan Munns @Lyonel

Hi @Hiten, Alternatively if you don't actually support translating of languages and only ever use "en-GB" then you can disable other language support and then all your portals will just use "en-GB" by default. The view to do this is in the admin tool should be under https://admin.hornbill.com/focussolutions//language/settings/ However if you do support other languages then as Keith mentioned you should setup translations per supported language in the portal config settings view. Cheers

Hi @Stuart Torres-Catmur, This will be fixed in the next release of the Admin tool. Cheers.

Hi @Caroline, Yes sorry that release note is a bit confusing. It is a new setting that is shipped with collaboration. When that is next released the setting will become available for you to set in the admin tool AND the administration tool will use the setting to set default font for the email templates editor. (collaboration email client will also use it as will service manager when they are released with support for it). Thanks,

@Martyn Houghton, So teams have other system dependencies like task assignment, being used in processes and application logic. By changing from a "team" to "department" would break those dependencies and I am assuming you want these parent teams, that are now departments, to retain those "team" features? I will see what platform team have to say about it. Cheers

@Martyn Houghton @Paul Alexander, So in the next release there will be a "is in" and "is not in" option. In the value box just use a comma separated values to check. a,b,c,1,2,true,false,null,undefined Note do not quote values....As the PC engine is client side it will perform an array.indexOf. So for example the above would result in something like:- ["a","b","c",1,2,true,false,null,undefined].indexOf(<thepcfvariablevaluetesting>) Cheers

@Martyn Houghton, Not sure why it isn't in there already. I will have a look at adding it and let you know. Cheers

Hi @Martyn Houghton, I believe it is hardcoded as a max. There is also a 30 second execution limit as well i believe. What i would suggest is run several queries with limit clause. So something like 1. select * from thetable order by primaycolumn asc limit 0 , 5000 - then export 2. select * from thetable order by primaycolumn asc limit 5000, 10000 - then export 3. select * from thetable order by primaycolumn asc limit 10000, 15000 - then export 4. select * from thetable order by primaycolumn asc limit 15000, 20000 - then export 5. select * from thetable order by primaycolumn asc limit 20000, 25000 - then export 6. select * from thetable order by primaycolumn asc limit 25000, 30000 - then export Know its a pain but think that is only feasible way using the UI. Alternative is you raise a request with support/cloud/account manager to get your data exported.

@Paul Alexander @Kevin Kennedy, Ok so checking the code the save button will only enable if the report is setup correctly. However I found an issue where if report has schedule and is set to email people then the validation check failed when validating the schedule delivery type and the save button would not enable. Can you confirm if the reports you are experiencing this on have a schedule setup and the delivery type set to email? So I have fixed this specific issue, relating to email delivery type validation not working as expected. If you can look out for it in next release (next week) and see if that resolves your save button issues. Cheers

Hi Paul, Answer to first question is no. I dont even think there is a flag against report table to even indicate a schedule was setup for it. Unfortunately the coupling between "things" (entities) and scheduled jobs is very losely set in the job metadata i believe...i will have a discussion with server team to see what can be done. I think the immediate quick win is to at least have a flag in report table to indicate a report has a schedule defined in it. Could then filter report table to at least show just those with some scheduling info set. 2nd one just sounds like a defect. I will have a look. Cheers.

Hi @AndyHill, We are going to need access to your instance to check legacy app option settings versus the new db based settings that new api returns. Also need to confirm that only happens with "service" and not "customer" portal settings. If you could contact support referring to this post and give them permission to access the instance and I can then just verify the data discrepancy. Thanks

Hi @AndyHill, Will take a look. I might get support to request access to your instance so i can see the data and what the api is returning. We will let you know if that is necessary and i will let you know what i find. Cheers,

Hi @Michael Sharp, It is in beta build and will be included in next live release which should be on Thursday. Cheers

Hi @Michael Sharp, We will have a look at adding something in that makes the boxes line up across the measures. Cheers

@Paul Alexander, Just a correction in what dave has said... it only updates "application forms" that are shipped with the app. It does not update "custom forms". The issue you are having with custom fields not being picked up will be something else and you should contact support so they can assist Cheers

Yup. The process should pick up the authorisers automatically. You will note if you add the auto auth node before you add a get authorisers call it will show you a warning on the node saying it cannot find flowcode node that is providing the automatic list.

Hi Martyn, The get authorisers by role (and the other one) returns a special variable that is an stringyfied array. The auto authorisation node picks up that special variable automatically. The "owner" field is not a field to indicate who authorisers are and should only contain a user or variable that contains a userId. I will add in some code to hide that special variable from the picker as it cannot be used for anything else than its intended purpose. Cheers

Hi @Gary@ADL, Will double check to see if we record previous stage task states within the BPM state. If we do we can add a feature to the variable picker to allow selection of a task from previous stages. I will let you know. Cheers

@Paul Alexander, The admin release is expected to go out on Friday morning. We had a few things to sort out during beta hence the delay. Cheers

@Paul Alexander, It is currently in our beta stream, has been for a couple of week, but we have been doing a bit of work on new login and trying to remove as much use of php as possible. Assuming i get no objections from the team in the next couple of days I am hoping to push out a live admin release this week. Cheers

@Paul Alexander , I will take a look at adding that in. Cheers