At the day of the event, join the meeting here:https://alteryx.webex.com/alteryx/j.php?MTID=m7f559ba824e6396139b30176fe58108a
Don’t miss our next Virtual Washington DC User Group meeting!
Date: Wednesday, June 29, 2022
Time: 1:00 PM – 2:00 EST
It will be a great opportunity to get everyone excited about Alteryx. Bring your questions, thoughts, and experiences!
With the new Community Events experience, you can register to attend a meeting with a click of a button! Simply RSVP "Yes" on the top right corner to see the webinar link to join the meeting!
We hope you can attend!
Washington DC User Group Leaders
Hey @Ben_Edelman & @CesarPicco, thank you again for inviting me to present at this quarter's user group! I've included our PDF that we went through as well as the workflow to this thread, if anyone has any questions or would like to brainstorm ideas, please don't hesitate to reach out.
Thank you again, have a great holiday weekend everyone!!
Thanks for sharing @DataPrepChad ! Would you happen to have examples of documentation standards? I know there's no right or wrong way, but we're starting to build out the alteryx team at my firm and I tend to overthink things like this.
Hi @tbuenaflor, you're right in that there is no right or wrong way, what we do recommend though is consistency. For example, we like to ensure that each workflow we build is branded using our company logo and colors in Comment tools at the top, with a description of the goal of the workflow beside it.
Regarding the actual workflow, we have color coded containers for different components, so maybe one color specifically for Inputs and/or Outputs, and others for different functions based on the nature of the business (often with company colors).
Finally, I recommend short descriptions for annotations (this tool does that), comments for groups of tools and an overall description of the workflow, and of course branding. Hope this helps!