Sure. When you pick your "Does not contain", make sure you go to the array section of the filtering options.  

How you have that written it won't work, no.   I usually make an array of those values, then do a "Not In (array)" comparison.

Your configuration should look like this.    

I would recommend going with 2, this is what I typically recommend. You do need to actually be able to authenticate as that user, and once you get the connections setup it's no different than how it works today. You just have to actually be able to log in as the user to create the connection.

No sorry, I forgot what it was called. It's the misc. action -> assignCategories function.

This can happen if you're updating a series of tasks on the same project. From what I can tell, sometimes Fusion runs faster than Workfront and so if Workfront is still trying to save the previous commit when Fusion calls the next, this error can happen. My suggestion would be to either add an autom...

The module that you're using is trying to create a new issue, which means it has to have a name.   Based on your description, I don't think this is what you want to do. It sounds like you're trying to move an existing issue and add a form to it, in which case you should use the misc. action -> move ...

++1 to this, wildly agree multiple business rules should be allowed for the same trigger event type.

If the reference ID just needs to count up, you can just store your number in a datastore, and count up every time you make a document, so your number would be   CL{Number from Data store}MMYYYY

You can set it up so that the dev can't create new connections in Fusion, but I don't think you can get it as granular as you are saying.