New Desktop - Cannot Change Workflow State (Cannot Add / Remove Field)

Question

Hi All, reporting a bug (or at least an infuriating difference!) between classic and new desktop, reporting this here as well as through our partner as it this sometimes seems to be a more effective path of reporting bugs that actually make it through to the necessary level of support! 
 I have a class called "Budget" which has a property "Total Value" - this property is set through a VAF script that does updates to various properties as part of event handlers, in New Desktop, when I try to move the budget to a new workflow state I receive an error: 
 Access denied.
You are not allowed to add, modify, or remove the property "Total Value". 
 However, if I revert to classic desktop and use the same workflow state transition the change occurs with no problem at all. 
 The odd thing is that the behaviour is inconsistent - if I create a new "Budget" and send it through the same state transition it occurs without any issue. I would love to help chase down this bug, as the VAF extension (and state transitions) are critical to us, but I can't see any more valuable error information available through new desktop!

Craig Hawker · Accepted Answer

Unfortunately that is the official way forward. 
 This forum is a peer-to-peer support forum and, whilst there are a number of M-Filers here, it's not something that we can put proper processes around. 
 I understand your frustration.

Craig Hawker · Answer

I understand the frustration, I really do. 
 At this moment in time our resellers have responsibility for first-line triaging of items coming from their accounts; they are closest to the implementations and have resources to reflect on whether these things are related to your implementation or software issues, for example. Should the reseller need to raise these up to us then we do have an official support portal where they can raise tickets, and these are tracked according to various processes (as I am sure you can visualise, as it's the same in many companies). 
 Whilst in many cases this works very well, I do acknowledge that in some contexts this adds an additional level of bureaucracy. 
 Hopefully one thing you will see from this portal is that it is very good at what it aims to do - provide peer-to-peer support for implementation, configuration, and customisation issues. It also is used to try to provide product-level support, at which point things sometimes do stutter; the community is simply not part of that official support process, so the impression that customers get is that doesn't work as well for this. This is why I will always push people back to the official process; that is designed for product-level issues and requests, and has proper means to track and process such inbound requests. 
 That said: what I can additionally highlight is that many M-Filers (such as myself), including a number of product managers (such as myself), do frequent these boards. Where you raise items like this they do often end up being by the correct people. But that process is much less formalised than the official one, and it too has its own complexities and nuances.

Craig Hawker · Answer

Hi. 
 The forum is not a good place to raise bugs. It's not tracked by our support teams, nor can it easily be escalated or reported on. Can you raise this via a support ticket?

New Desktop - Cannot Change Workflow State (Cannot Add / Remove Field)

Top Replies

Contact Us

Schedule a Demo

Careers

Trust Center

Privacy Policy

Security Hall of Fame

Subcontractors

M-Files Community

Support Portal

M-Files Empower

Download M-Files

Product News