Victor

@Keith we're exploring some options to integrate with PowerBI (made some progress too)...with this, such reports as the one you presented should be doable... but with current reports... you have 4 dimensions here (so to speak)... SLA expectation, SLA Status, Service and Frequency (Months) ... I don't think you can do 3 with current reports, not to mention 4 ... multiple widgets/measures would be the way to do this with current functionality I think...

@Joyce sorry for the delay. Took the liberty to create a test widget in your instance (Hornbill Test - Aged Incidents), hope this is all right... is this what you were looking for?

@Paul Alexander it seems when you update a request manually, Service Manager will also trigger a "process resume" action...which is not happening on automatic updates... ... I'll ask our dev team about this, to see what they think of...

@DeadMeatGF ahh.... indeed (just watched some updated trailers on it, there goes my morning work ) ... I thought (wrongly of course) they will take the story to find out the humanity creators... but taking it toward the Alien path is good as well Although I would not mid to see the Engineers ...and everything about them

@Paul Alexander ermmm.... good question .. I have no idea to be honest, I'll have a look in the flowcode to see if is build to only act on manual updates... I assume you tested this now, do you have a call reference with the test? I also want to look in the logs and trace the flowcode execution...

@DeadMeatGF I've only seen a trailer a while back, but wasn't supposed Covenant to take further the Prometheus story? Which is what happens when David and Elizabeth fly the Engineer ship to their home planet? ... I see mixed info now that Covenant is a spinoff of sorts... I might be talking rubbish since I am not up to date with the news...

I've told you, @DeadMeatGF never place your trust in us. We're only Hornbill. Inevitably, we'll only disappoint you. I really hope not!

@Ralf Peters dev team is looking into this now... almost forgot...if you plan to update SM, please let me know when you do... I might need to put back the fix since it might be overwritten by the update...

@Ralf Peters and I assume the email to contact is also being sent.... ? looking through the logs from 05/05 when SR00024703 was raised to see what was different then...

@lee mcdermott @cchalmers issue is now fixed. We deployed an update to SM which contains the fix. You would need to update SM app to have the fix available in your instance.

@Paul Alexander issue is now fixed. We deployed an update to SM which contains the fix. You would need to update SM app to have the fix available in your instance. @Martyn Houghton forgot to mention you as well so FYI

@Martyn Houghton more like I was too slow to update the thread with the notes

@Martyn Houghton refresh ... F5 I mean

@Ralf Peters right, so the "nofifyEmailContact" operation is triggered by BP in the context of the user.... in the examples you mentioned the user is a basic user which is missing rights to certain tables... this is why the node fails... ...don't think is a configuration issue, need to check this with our dev team, could be that we not doing something right in Hornbill... meantime I put in place a quick fix, however since I (admin) am not a basic user I am unable to test it fully... would it be possible to ask one the the users that were logging these requests to do a quick test for you/us? I have cleared the error from the requests you mentioned (except from SR00024863, this one seem not to have the error)

@Ralf Peters I need to have a look at these requests to find out what's going on... please bear with me

@Sonali here is a possible cause and solution for the error you encountered:

@SJEaton @Paul Alexander @Sonali Thanks to @Trevor Killick we believe we found why the error occurs. You have a progressive capture with custom forms. One or more of these forms have one or more fields as dynamic checkbox or list which is missing some configuration (the data provider most likely). Can you please review your configurations and make sure they all dynamic fields have the full configuration?

@cchalmers can you log a request/incident as well please? Thanks!

@SJEaton @Paul Alexander As I mentioned in the below thread, it does (or seems to) occur when doing "Save and Activate" ... If you do just "Save" then you go to ProCap list and activate via the On/Off button...

@lee mcdermott we need to investigate this with support. Would you mind raising a request/incident via a web form here: https://www.hornbill.com/support/?request/ ?

@Paul Alexander is done. You won't see the field value in the UI (due to the defect), but is there

@Sonali I assume you getting this when you try to "Save and Activate" ? If so, you can just Save it then from ProCap list, turn the Active button ON... We seen this error recently and currently investigating it.

@Paul Alexander @Martyn Houghton we currently investigating this. @Paul Alexander we can add the reference for that rule if you like, what was what you wanted to have in the reference field?

@Martyn Houghton afaik there is an app setting (app.email.routing.rules.emailConfirmation.newRequest.sendConfirmationEmail) which can do this ... without the need to get the BP involved... haven't tried it though...

@Sonali you have one request with status.new... which seems not to be showing in user app.... @Ehsan, should status.new show in requests list?