We've recently made an accessibility improvement to the community and therefore posts without any content are no longer allowed. Please use the spoiler feature or add a short message in the message body in order to submit your weekly challenge.

Weekly Challenge

Solve the challenge, share your solution and summit the ranks of our Community!

Also available in | Français | Português | Español | 日本語
IDEAS WANTED

We're actively looking for ideas on how to improve Weekly Challenges and would love to hear what you think!

Submit Feedback

Challenge #105: Think Like a CSE… Tools are missing!

ReconBen
8 - Asteroid
Spoiler
ReconBen_105.PNG

MUHAMMED_NABEEL_P
8 - Asteroid

Nice challenge..

TheOC
13 - Pulsar

Quite a fun one - and nice to reinforce some knowledge on troubleshooting issues!

Spoiler
step 1:
Load the workflow, and see whats wrong:
TheOC_0-1633705023104.png


Its clear the macro hasn't been exported with the workflow.

Step 2:
download the macro, and implement into the workflow:

TheOC_1-1633705096811.png



Step 3:
change parts of the configuration to match what is in the XML of the broken macro:

TheOC_2-1633705131653.png

TheOC_3-1633705197418.png



Step 4:
Delete broken macro, and replace connections:

TheOC_4-1633705223828.png

 

TheOC_5-1633705237199.png


Step 5:
Run and make sure it works fine:

TheOC_6-1633705541913.png


Step 6:
saving the workflow.
Save the workflow to the desktop:

TheOC_7-1633705611518.png

 


Export the workflow:

TheOC_8-1633705623870.png

Ensuring the macro is selected:

TheOC_9-1633705639901.png

 


All done!


binay2448
11 - Bolide

Find attached my solution for the same...

Chantelb
9 - Comet
Spoiler
Used Alteryx to find and edit the workflow .xml to the correct path and then write out the corrected workflow.
Chantelb_0-1635311105211.png

 

MichMatt
8 - Asteroid

I'm book marking this for future macro troubleshooting!

DalilaSalinas
7 - Meteor

done