Community Spring Cleaning week is here! Join your fellow Maveryx in digging through your old posts and marking comments on them as solved. Learn more here!

Washington, DC

Welcome to the Washington User Group

Click in the JOIN GROUP button to follow our news and attend our events!

Q2 2022 Washington DC Alteryx User Group Meeting

UserGroups_EmailHeader-2021.png
Published on ‎06-24-2022 12:56 PM by | Updated on ‎06-27-2022 08:56 AM

Don’t miss our next Virtual Washington DC User Group meeting!

 

 

Date: Wednesday, June 29, 2022
Time: 1:00 PM – 2:00 EST

 
Agenda:
1:00-1:05 - Welcome
1:05-1:15 - Community Updates
1:15-1:20 - Inspire Recap
1:20-1:50 - Data Prep U Presents: Alteryx Tips and Tricks
1:50-2:00 - Q&A, Wrap-up, Open Discussion
 

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



Event has ended
You can no longer attend this event.

Start:
Wed, Jun 29, 2022 10:00 AM PDT
End:
Wed, Jun 29, 2022 11:00 AM PDT
Labels (1)
5 Comments
DataPrepChad
10 - Fireball

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!!

 

~ Chad

cmartin@dataprepu.com

tbuenaflor
7 - Meteor

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! 

Awesome @DataPrepChad !!! That makes sense, thanks for the outline and summary! 

FláviaB
Alteryx Community Team
Alteryx Community Team

Thanks again for presenting at our Q2 Washington UG meeting, @DataPrepChad. Would you be able to assist @tbuenaflor with his request? 

Flávia Brancato