Text for messages and add slack to application process

[mcdougles]

Please add a Text message property (text + property values + scripting). Add Slack notification possibility to Application process

[nhmathis]

Hi,

Any modifications to the Application Process's steps will require changes to the core product. The plugins in the IBM-UrbanCode GitHub or Microsite do not control any Application Process steps.

Your best workaround will be creating a simple generic process, adding the Slack step to the generic process, and running the generic process through an Application Process. Through some property use, you can pass a value from the application process into the generic process.

-Nick

[mcdougles]

Hi

That's what I'm doing.

What about the text message?

Regards,

Zoltan

2017. dec. 12. du. 4:03 ezt írta ("Nick Mathison" <notifications@github.com

      ):

Hi,

Any modifications to the Application Process's steps will require changes to the core product. The plugins in the IBM-UrbanCode GitHub or Microsite do not control any Application Process steps.

Your best workaround will be creating a simple generic process, adding the Slack step to the generic process, and running the generic process through an Application Process. Through some property use, you can pass a value from the application process into the generic process.

• Nick

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/IBM-UrbanCode/Slack-UCD/issues/8#issuecomment-351076761, or mute the thread https://github.com/notifications/unsubscribe-auth/Ag4mFbUl2t5p4-7jbSylfIfEbmNUgZwZks5s_pVCgaJpZM4Q_Esg .

[nhmathis]

Which step are you using? Both steps allow you to supply a message value.

For the Attachment Notification step you will need to write the main body of the Slack message. That documentation can be found here. Specifically the Attachment structure section.

[mcdougles]

I'm using "Post Notification to Slack" step.

[image: Szövegközi kép 2]

Which property is for the message body?

2017-12-12 16:37 GMT+01:00 Nick Mathison notifications@github.com:

Which step are you using? Both steps allow you to supply a message value.

For the Attachment Notification step you will need to write the main body of the Slack message. That documentation can be found here. https://api.slack.com/docs/message-attachments Specifically the Attachment structure section.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/IBM-UrbanCode/Slack-UCD/issues/8#issuecomment-351088462, or mute the thread https://github.com/notifications/unsubscribe-auth/Ag4mFTMQmCwM7NiUM84KcnurEYrTFAnkks5s_p3LgaJpZM4Q_Esg .

[nhmathis]

My apologies, I was incorrect in my earlier comment. The Post Notification to Slack step was intended to report the status of a Component Process version import. Thus, it will report the status (success/failure) of the component version specified.

You will want to use the Post Attachment Notification to Slack step to create a specific message. Use the documentation linked above to generate your own message.

[mcdougles]

Thank You.

2017-12-12 20:15 GMT+01:00 Nick Mathison notifications@github.com:

My apologies, I was incorrect in my earlier comment. The Post Notification to Slack step was intended to report the status of a Component Process version import. Thus, it will report the status (success/failure) of the component version specified.

You will want to use the Post Attachment Notification to Slack step to create a specific message. Use the documentation linked above to generate your own message.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/IBM-UrbanCode/Slack-UCD/issues/8#issuecomment-351160948, or mute the thread https://github.com/notifications/unsubscribe-auth/Ag4mFejeoaVWx1N9UctWv0n3ffGAu8U4ks5s_tDhgaJpZM4Q_Esg .

[nhmathis]

No problem.