Daniel Dekel

Hi Mark, Thanks for your suggestion. We've done the change and you will see it in our next release. Kind regards, Daniel.

Hi Samuel, I think I understood the problem you have. The actual label or question is always displayed, so what you want is to hide it and display only the value with WiKi Text. For this I think the best thing will be to add a new field type "Label" as you suggested. But instead of giving an option to set the font size, it will accept WiKi text, that is more flexible because you can play with many other properties of the text such as italic, bold and icons. I will raise a Change request for this. Although it's not that difficult to implement i dough you will see it soon (like in a week) because it requires changes in multiple products, Core, Platform, Admin Tool and Service Manager. I will let you know when is ready for you to use. Thanks, Daniel.

Hi Martyn, OK, we are now looking at the problem. Will update you as soon as we have something. Thanks, Daniel.

Hi Martyn, I asume the error message is in the Admin Tool, when you design the Progressive Capture, correct? Daniel.

Hi Lyonel, What you ask definitely makes sense. I can't give you a date, but I will add a change request and inform you when it is ready. Thanks, Daniel.

Now that we have identified and fixed the problem I wanted to provide you with a more detailed explanation of the problem, how it came about and what we have done in order to ensure the problem does not occur in the future. In deploying the latest release of the Collaboration Core we unfortunately introduced a defect that prevented from sending emails from some applications, Service Manager was impacted. The problem came about because of a mismatch between the version of the platform API and the new version of the user app. The user app and client libraries assumed a specific feature from the platform was already available but it was not present and the effect was the platform wat unable to select the from address when sending an email. Traditionally the platform/API runs ahead of all other development but recently we have been advancing on our dev stream faster and in this case we failed to have suitable dependency checks in place at the release stream level - which meant core library changes were published in advance of the feature being available on the platform/API. This was a failure in our deployment process which we have identified, and have now put steps in place to ensure that these dependencies are enforced so publication will be prevented when any such dependencies exist in the future. We are sorry for any inconvenience caused this morning, we take the quality and reliability of our service very seriously and feel it is very important to be transparent and open with our customers. If you have any specific questions about this I will be very happy to answer them. Thanks, Daniel.

The problem has now been fixed. You will have to refresh your browser. Sorry for the issues caused. Daniel.

We've found the problem and is going to be fixed in a few moments

Hi @Martyn Houghton IDOX Group , The problem PM00142208 was fixed and is now in Live. Please let me know if you find further issues. Thanks, Daniel.

Hi Martyn, Just to make it clear, to manage Achievements you can login with a user that has the Admin Role and that will be enough. If you don't want to grant a specific user all the rights you can create be more specific with a role and create a new one as Miro suggested. But in general, we suggest customers to use the Admin Role for this otherwise we can end up having many many roles, each for a small peace of functionality. That's why you have the option to create such roles if you want. Hope this helps, Daniel.

Hi, That Flowcode is deprecated and we are planing to remove it soon. There is a new API session::userProfileGetList but is still being unstable and we are working on a server release that will provide several fixes. All this is a part of a rework of the entire profile area. Let me know if you need more help on this. Regards, Daniel.

Hi Martyn, Wanted to inform you that as part of this change, we've added an option to sort the Simple List by Label or Value in the form designer. This in not the final solution but is a step closer to what we want to achieve. You will be able to see this in the next update of the Collaboration Core, should be within a few days. I'll keep you informed about our next changes. Thanks, Daniel.

Hi Samuel, The problem was fixed and will be released in the next Service Manager update. Thanks, Daniel

Hi Mike, Please refer to this previous post Thanks, Daniel.

Hi Michael, yes, it's by design and as DeadMeatGF mentioned, it was inspired by many other collaborative platforms.

Hi Samuel, I've raised a defect for this ( PM00142447 ). I'll keep you informed when this will be fixed. Thanks, Daniel.

We will release it internally this week for testing but unfortunately I doubt we will be able to push major releases during August, maybe end of August. It will be coming as experimental in the next few weeks, and you will be able to turn it ON but I suggest waiting for it to be more stable. We will send a notification (Harry Hornbill) once it is available. I can asure you it will be a big improvement to what you have now! Thanks, Daniel.

Hi Greg, We are now working on a complete new view for reading email. I'll add your request to the list of features to implement. Thanks, Daniel.

Hi Samuel, Sorry for the delay. I was trying to see if is possible to implement your idea and it is. I'll let you know when can this be done. Thanks, Daniel

Hi, The categories list issue should be fixed in release 32 (Categories do not update unless refresh). Please let me know if you have that version and it still does not get updated. If is not working, can you also let me know in what view you don't see the update? Regarding the time against a category, is not that you put time against Sub-Category only, it will require the combination of both of them. We don't have plans to change this. We've also added a more visible validation error if you don't select the sub-category. It will come in a close release. Thanks, Daniel.

Hi Martyn, Actually in the back-end the contact is archived and if is connected to a portal it is unlinked from the portal. We haven't implemented yet the option to show archived contacts in the list nor to un-archive as in the Organisations. Once we add that functionality you will be able to see all the archived (deleted) contacts. Hope this helps, Daniel.

Hi Dave, Please refer to this previous post Thanks, Daniel

Hi, We'll have a look at this. Probably something can be done to give better visibility at the different types of checkpoints and their statuses. I'll let you know. Thanks, Daniel.

Hi, I've attached an image that will hopefully make things more clear. Basically as long as you set a category and set some time, it will be added to your timesheet records. If you don't set any of these, it will not be added. You can set default categories to avoid seeing these warnings all the time by going to: Manage Categories -> Manage Default Categories -> Select the email one and set defaults. Thanks, Daniel.

Hi, That button is not related to logging Request, you can use it to measure time against that particular email. It shows the warning symbol because no default category has been assigned. I can see that the confusion could come because the icon is quite similar to the one used for an Incident. I'll make sure is changed. I hope is more clear now, Thanks, Daniel.