Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

duypnguyen
duypnguyen
Online

Badges

Badges
21

Accepted Solutions

Accepted Solutions
36

Likes Received

Likes Received
42

Posts

Posts
209

Discussions

Discussions
35

Questions

Questions
174

Ideas

Ideas
0

Blog Posts

Blog Posts
1
Top badges earned by duypnguyen
Customize the badges you want to showcase on your profile
Re: openwhisk alarms not allowed on local environment - App Builder 31-08-2020
hi @Urs_Boller - here are my test values. Worked fine.startDate: "2020-08-31T14:20:00.000Z" stopDate: "2020-08-31T14:22:00.000Z"

Views

722

Likes

0

Replies

0
Re: Trigger another action from within an action - App Builder 31-08-2020
Hi @Urs_Boller , it is recommended to leverage the openwhisk npm to programmatically call actions, triggers, etc.In terms of implementation, there could be a few ways to achieve what you need:- If you only want to invoke one action when the condition is met, you can invoke that particular action only.- If you want to invoke several actions when the condition is met, you can map a trigger to those actions by rules (trigger --> rule A --> action A, trigger --> rule B --> action B). Then you only i...

Views

428

Like

1

Replies

1
Re: openwhisk alarms not allowed on local environment - App Builder 31-08-2020
@Urs_Boller, the alarms are run in UTC. Did you set your stopDate in UTC?

Views

750

Likes

0

Replies

0
Re: openwhisk alarms not allowed on local environment - App Builder 31-08-2020
Ah ok, that's good to know. Great idea! Then your scheduled action doesn't have web exposure, only being triggered then saving data to the state lib. And your "display UI" action would have `web: yes` to return the data to the UI.

Views

751

Likes

0

Replies

0
Re: openwhisk alarms not allowed on local environment - App Builder 31-08-2020
Hi @Urs_Boller.Yes that's right, without `web: yes` your action can only be invoked by a trigger or directly by you in command line (aio runtime action invoke). Not possible to trigger from outside. IMO it makes sense from a security perspective, because you are assured that there is only one entry point per entity.From the other thread I understand that you want to expose the same action functionalities to the UI as well. I would propose to create a (npm) library for the common methods of the s...

Views

759

Likes

0

Replies

0
Re: openwhisk alarms not allowed on local environment - App Builder 31-08-2020
Hi @Urs_Boller, here are answers relevant to your questions.Answer 1: It is not possible to deploy an alarmed trigger in `--local` mode, because the alarms provider and packages are not deployed in your local openwhisk. You have to deploy it on I/O Runtime (without `--local`).Answer 2: I tried the same setup as yours and it seems to work for me. The only difference is, I set the `require-adobe-auth` flag to false and removed `web: yes`, because the alarm is not able to provider a token as a web ...

Views

779

Like

1

Replies

10
Re: Adobe credentials for standalone actions execution - App Builder 25-08-2020
Hi @Urs_Boller, in that case you first need to remove the web-src/ folder to make your app headless instead of SPA, so that JWT token can be validated. aio app delete web-assets To test the token, you could retrieve it from I/O Console, under "Generate JWT token" in your project, and pass it in the request header to your action, e.g. `Authorization: Bearer ey1234567890....`.To have the token generation in action code, you could leverage the Adobe IMS SDK . Please note that, it's better not to ex...

Views

469

Likes

0

Replies

0
Re: Adobe credentials for standalone actions execution - App Builder 25-08-2020
Hi @Urs_Boller , first of all it would be good to identify whether your app is an SPA or headless, as described in the Security Overview . I assume you have the `require-adobe-auth` flag set to true for your actions.If it is an SPA, the user token must be passed from the Adobe Experience Cloud (ExC) Shell, specific to the user session you are logged in.If it is a headless app, you need to pass a service token which is obtained with the JWT auth flow.You could also use a user token in a headless ...

Views

493

Likes

0

Replies

3
Re: split actions or not? - App Builder 24-08-2020
@Urs_Boller, the returned payload of your first action would be in the input params of your second, and so on. The returned output of the last action in the sequence would be its response payload in the end.

Views

664

Likes

0

Replies

0
Re: split actions or not? - App Builder 24-08-2020
Good discussions over here. Chaining of action in I/O Runtime (or Openwhisk at its core) is called sequence, which you can read more about here: https://github.com/AdobeDocs/adobeio-runtime/blob/master/reference/sequences_compositions.md#sequencesExample of sequence definition in the manifest.yml of a Firefly project:sequences: authenticate: actions: 'login, check, redirect' web: 'yes'

Views

677

Likes

0

Replies

0