Gerry

@DeadMeatGF ah ok, that makes perfect sense, so having a "hold until day" is actually a very sensible and useful function I would suggest. I am sure we can do something for it, sounds simple enough. Gerry

Why not used scheduled tasks for those checks @DeadMeatGF? Hope you are recovering well? did you get a chance to look at those questions? Gerry

There is no reason why a Flowcode node could not be create to do this, its a pretty simple check. You would need to raise that as a feature request so I am mentioning @James Ainsworth who can get this added to the SM backlog, not sure how quickly we could fit something like this in, but we do very much you appreciate participating in one of our spotlights so am happy to help out if we can. James, it would be along the lines of a flowcode node that given the current date, would take an input param of day and would return outcomes of match/no match. Gerry

@Martin.bowman This (being the in-app reporting) is still work in progress, I think @James Ainsworth can give you a better update on this progress than I. However, you state that you have a "number of Dashboards" so I presume you mean existing dashboards that you want to allow your team members to view, this is not something we have in development, they would need to use the admin view, although you can lock down the rights they have in the admin tool to just the dashboard view and can control who has the rights to see each dashboard. This can all be done through roles and rights. Gerry

@Lyonel Ah ok, yes both PC and BPM are global components of the platform so this would be the case absolutely. Thanks for the clarification. Gerry

@Lyonel The versioning is possible I am sure we can look to add that to the backlog. Not sure what you mean by "And across all applications?" if you could clarify that I would appreciate it. Gerry

Hi Mark, Can you expand further. Activities from a schedule? or bpm? or manual? any errors reported? Gerry

@Martyn Houghton @samwoo There is no reason not to use the API's to maintain these from external systems/scripts, it would be easy enough to achieve. Gerry

@Dan Munns Yeah that makes sense, quite a common scenario. I think setting up trust relationships would be the best way to go if you can Gerry

@Martyn Houghton Yeah thats on the list of things to do, we can show the certificate information easy enough. Gerry

@Martyn Houghton Ok thanks, 70 seconds is not going to have any effect in relation to the problem you are reporting, I found a slight issue around the skew setting being incorrectly applied but this is not related to your reported issue. As @trevorharris suggests, this would appear to be a ADFS rollover window. Gerry

@Martyn Houghton What do you have this system setting set to? security.saml.timeSkewCompensation Gerry

Dan, You can set up any number of SSO profiles on the Hornbill platform, so you could have one SSO profile per domain. When a user browses the portal they would need to select which profile to use when logging in. Thats quite messy though for your situation. What would be better would be for your AD admins to pick one domain to work with and then set up trust relationships to the other two domains, it should then be possible to use a single SSO profile for all users regardless of what domain/AD server they are on. I have seen this done many times. Perhaps a more general question, but why do you have three separate domains/AD deployments? Is there any plan to unify them in the future? Gerry

Andy, In the admin tool, navigate to Home -> System -> Email -> Shared Mailboxes -> (your mailbox) Click on the "Inbound Mail Services" tab and you should see one or more mail connector configurations (either IMAP4 or POP3) Open up the connecter and you will see a "Test" button, that will try to connect and if it fails (which it most likely will) it will give you some diagnostics information. We cannot see any problems our end so its most likely something internal to your network/firewall/mail server, Let us know what you find. Gerry

Hi Keith, Ok that makes more sense now. So the problem is, a mass export. So you somehow (lets leave aside for now how) you get a selection of tickets, say 50 of them, and you print them. What about the attachments, what do you do with them, export them into a folder structure? So what would you provide the auditors, a print out or a bunch of files in a folder structure. In my experience auditors don't like having to deal with files they like everything printed, the requirement to look at attachments on requests will make that very complicated and all sorts of technical complexities. Its quite a specific requirement, I am not sure building it into the tool would be terribly useful for most customers. Possibly we (or your guys) could build an extract tool as an open-source command-iine tool where you feed it the criteria, it uses our API's and WebDAV to get the request details and the file attachments and it makes you an audit pack. I like the idea of having audit extracts from the system, that would be a very good "enterprise-class" feature but I am not sure how that would sit in the priority list for the Service Manager dev team, it would be quite a big task to get it done. Is this something that is urgent for you? If it is, and you could work with a command-line tool for extract, you could possibly consider our expert services team who I have no doubt could build something like this for you with relative ease? Gerry

@Darren Rose Ok well that sounds like it might work for you. Do you envisage any specific integration requirements between the Products you manage and Service Manager? I ask because as of now the work on Product Manager has been as a stand-alone App, not an extension to Service Manager. Gerry

Keith, Can you be more specific, "extracting attachments" is very broad in scope. Perhaps you can give me an example of what you need do to? Attachments can of course be accessed and therefore extracted individually, but I think you are asking for something different. What would the SarbOx or FDA auditors want to see exactly? Gerry

Hi Darren, What do you guys currently use to do this? Do you guys create software? Gerry

@Martyn Houghton That would be a question that I think @James Ainsworth would be better equipped to answer, I am not sure where this requirement sits within our current dev priorities. @James Ainsworth can you add anything here? Gerry

@samwoo Thanks for the explanation. I seem to have misinterpreted what you meant when you said "creating brand new software from scratch or making changes existing software" In which case what I was proposing is not for you, I would suggest what you need to be using is change and release management functionality provided within Service Manager which is designed to do what you want which is manage the release cycles of COTS software and hardware configurations. A release can have one or more CHANGES and PROBLEMS associated with it, and of course a release is considered complete when all CHANGES and PROBLEMS associated with it are implemented/resolved. I am not an expert in the detailed workings of Service Manager, @James Ainsworth would be able to jump in here and offer more guidance. Gerry

Hi Sam, Yes I am pretty sure when we put text content like a phone number into the XLSX format we put it in as text and not as a formula/numeric value. I would need to check to be 100% sure but you can take it thats correct, if its not I would consider that a defect. Gerry

We already have a "Product Manager" app under development. It handles (or is planned to handle) the following major data entities. Products Components Releases Defects Features The basic aim of the application is to provide product lifecycle management. Once a product is defined, you can create releases. Released have a lifecycle so Planned, In Progress, Released as well as a status, Alpha, Beta etc... A release is essentially a container of Releases and Defects against a product. A release is considered feature complete when all Features associated with the release are implemented and all Defects associated with that release are Fixed. The application will allow you to manage/generate release notes etc. The Portal interface will provide a way for customers up-vote/down-vote features and defects, features and defects will also have a lifecycle, when they are open they will either be in the product backlog, or they will be associated to a release. Thats a very high level overview but thats the essence of the high level specification. The application is targeted at "Software Companies" who make and support software products they make. You can achieve the same thing using Service Manager, mapping problems to defects, enhancements to changes and releases to releases but I felt that the business of managing software products has some very specific needs that if we tried to meet with Service Manager would either be very hacky or would take Service Manager off in the wrong direction. I have no target date at the moment, the development work so far as been unprioritized. If there is sufficient interest from say 3 to 5 companies already using our platform who would like an app like this that we can wok with, and who would be willing to help drive the feature set and once built be willing to do a case study I would be keen to put together a working group and prioritise development of the application. In exchange for that early input, testing and roll-out I would of course offer those companies the use of the app for free, for life. @samwoo does that sound like the sort of app you are looking for? Interested? Anyone else interested at this point in time? Gerry

Hi Claire, Everyone will get this as soon as its in preview, you will see a Harry Hornbill notice once its rolled out. We wont be doing email distribution at this time, we are using Document Manager as the distribution mechanism because we get more functionality and of course it makes the reports more collaborative. Gerry

Its interesting looking at this, it would seem that most all platforms support this, its actually a valid approved unicode character https://emojipedia.org/reversed-hand-with-middle-finger-extended/ The daily emjoji selection is just random but its somewhat unfortunate selection Gerry

Hi Hayley, It is certainly not considered an appropriate emoji to "use" at work. I was not specifically added, I think its present because its part of an open emoji icon set/library we use so I will need to have someone investigate weather or not this can be removed/disables, I expect it probably can. Gerry