AlexTumber

@Nikolaj thanks for your post. This is an area that we would like to improve for sure. The only way I can think of currently is to add all of the relevant project tasks to a board and organise the lanes by project member. Alex

@Ben Paddick sorry to hear this is still causing issues. When you say: I'm slightly confused as to when api you are calling. Can you confirm how many api calls you are making and in which order? Alex

@Ben Paddick I should have spotted this sooner: You need the ProjectTasks entity and not the Projects entity. So # Invoke XMLMC call, output returned as PSObject $xmlmcOutput = Invoke-XMLMC "apps/com.hornbill.projectmanager/Projects" "addProjectTask" should be: # Invoke XMLMC call, output returned as PSObject $xmlmcOutput = Invoke-XMLMC "apps/com.hornbill.projectmanager/ProjectTasks" "addProjectTask" I will ask internally about changing the error message to better reflect the issue. Alex

@Ben Paddick I can only assume that this is a fault with our powershell module because if the error being returned is this: : Failed to load FlowCode script '\\?\D:\Hornbill\ESP Server\instances\vinci\apps\com.hornbill.core\entities\Projects\fc_ops\addProjectTask.xml'" It can only mean that the app path is hardcoded to com.hornbill.core when it should be configurable to allow you to inject an app, which in this case would translate to com.hornbill.projectmanager. I will raise this internally and reply to this thread when I have an update. Alex

@Ben Paddick I don't think it is. Is this now working for you? Alex

@Ben Paddick It looks like the path is wrong. Instead of: \\?\D:\Hornbill\ESP Server\instances\vinci\apps\com.hornbill.core\entities\Projects\fc_ops\addProjectTask.xml' It should be: \\?\D:\Hornbill\ESP Server\instances\vinci\apps\com.hornbill.projectmanager\entities\Projects\fc_ops\addProjectTask.xml' Alex

I should add that we will update the documentation on the project task api's as this is not clear. The reason the outcomes param is like this is because in the future we will be giving our customers the opportunity to create custom outcomes for their project tasks. Alex

@Ben Paddick sorry to hear you are having problems. Looking at your api call, the JSON for the outcomes param should be something like this: [{"outcome":"completed","text":"Completed","language":"en-GB","buttonColor":"primary","requiresReason":"false"}] Can you let me know if this works? Alex

@Dan Munns thanks for your post. This is an area that is currently being expanded so expect to see some changes there shortly. Alex

@Nick Brailsford sure no problem. All feedback (both good and bad) is most welcome :-) Alex

Hi @Nick Brailsford Sorry to hear that. I'm not sure what the problem is without seeing it but perhaps it has something to do with permissions. I will ask our development team to try and recreate the issue. Regarding simple lists, although you can create them, you can't yet assign them to custom fields on the supplier or contract forms. This will be introduced very shortly as a new feature. There are 2 ways to create both supplier contact and contracts. You can quickly create them (filling in minimal information) or by clicking the More... button you can open the form in full screen mode. Once created, the contacts and contracts should be added to the accordion and shown like so against the supplier: Alex

Great stuff, thanks @Nick Brailsford

@Nick Brailsford our development team have found and fixed the issue. It is resolved in the next Supplier Manager update which is now available. Alex

Hi @Nick Brailsford, thanks for your post. I will ask our development team to investigate. Alex

@Nikolaj thanks for your post. I will ask our development team to investigate. Alex

@Dan Munns Upon investigation, all the button was doing was opening the email popup and not even attempting to insert a 'to address'. I'm pleased to say that this behaviour has been changed and will be available in the next Supplier Manager update: Alex

This issue has been identified and fixed by our development team and will be available in the next update.

@Paul Alexander are all the milestones and tasks set to 100% progress and have a status of Completed? Alex

@Lyonel thanks for your post. All I can say is that this is in active development and we are disappointed not to have been able to release it before the start of 2019. When there is some more news on this I will post back to this thread. Alex

@Nikolaj thanks for your post. This is still an area that we are working on and hope to have addressed soon. Alex

@Darren Rose thanks for your post. I will pass this onto our development team. Alex

@Lyonel yes there are definitely plans to increase the system's capabilities and to offer multiple progressive captures and custom forms. This is one area of Project Manager that will be focused on once we introduce other features that have been prioritised. Alex

@Lyonel thanks for your post. Although the addition of custom fields is still in our plans, it would be great if we could offer specific fields by default that would be of use to multiple customers. This of course works out best for everyone. Can I ask what in particular you would use custom fields for on a project? Do you have fields that are specific to the types of projects you run or maybe fields that are specific to your organisation? Alex

Hi @Dan Munns thanks for your post. I will ask our development team to investigate. Alex

@Dan Munns thanks for your post. This looks like a bug to me. I will pass this onto our development team. Alex