duypnguyen

Adobe Experience Manager

Adobe Campaign Classic

Adobe Campaign Standard

Adobe Experience Platform

Adobe Analytics

Adobe Audience Manager

Adobe Target

Adobe Experience Cloud

Adobe I/O Cloud Extensibility

Adobe Advertising Cloud

Marketo

Magento

Adobe Creative Cloud

Adobe Document Cloud

Workfront, an Adobe company

Your achievements

0% to

Tip / to gain points, level up, and earn exciting badges like the new

Open Alerts Bar

Community profile duypnguyen Employee

Job title here

Location here

15 BADGES

Learn more

Joined the community 24-01-2018 10:58:02 AM

Online

View leaderboards

Profile

Trophy case

Top badges earned by duypnguyen

Boost 3

Re: Is there a URL to get the demoed code from Git? (IODevena... - Adobe Experience Manager

@andrija_sm - that was an internal git repo and not accessible to external users.The demo was simplified and published as a sample app here: https://github.com/AdobeDocs/adobeio-samples-aemaacs-assets-custom-ui

Re: You're right, sorry for the confusion. And yes, pursuing... - Adobe I/O Cloud Extensibility

@kishoreindraganti - the payload limit in Runtime is 1MB, more details at: https://www.adobe.io/apis/experienceplatform/runtime/docs.html#!adobedocs/adobeio-runtime/master/guides/system_settings.md.To deliver larger payload you can leverage a cloud storage, for example upload your files to S3 and return a redirect response from your action to the file URL.

Re: Announcement: Adobe I/O Runtime: Node 14 Support Added - Project Firefly

@Anil_Umachigi - thanks for trying out the nodejs 14 runtime.You should have this combination: aio-cli@7.0.0, node 14, supported version ^14 in package.json (try removing package-lock.json and node-modules to purge all existing dependencies).And you are right - new apps will be node 14 by default (supposing your local machine has the above setup)

145

Re: Understood what you mentioned but my question is HOW to c... - Adobe I/O Cloud Extensibility

@1982luca - thanks for confirming that you were able to create the event and webhook. Let us know if you have further questions.

Re: Size limit on request headers in IO - Adobe I/O Runtime

@karan_sharma_di - do you have the issue with Adobe I/O Runtime specifically (running serverless action)?From the description it sounds like a question for the API Gateway?

Re: Can we use Java runtime? - Adobe I/O Runtime

@hegarg - For now, Adobe I/O Runtime only supports Node.js.Please refer to this page for all the supported runtimes currently.

Re: Understood what you mentioned but my question is HOW to c... - Adobe I/O Cloud Extensibility

@1982luca - I still don't know which event source you want the events to come from.In short, the source triggers the events and you can receive those events through external webhooks or Runtime actions.It is not clear to me what you meant by triggers and events in this context. Can you please elaborate?

106

Re: webhook - Adobe Console I/O and Adobe Runtime I/O - Adobe I/O Cloud Extensibility

@1982luca - the options you see here are the source of events. You could select CC Libraries, Adobe XD, AEP, etc. If you have an external source of events, you could also try out Custom Events as part of Project Firefly. Here is a codelab showing how to set it up: https://adobeio-codelabs-custom-events-adobedocs.project-helix.page/.The webhook, Runtime actions and Journaling API are options for delivery of events. You will see them in a later step of this configuration wizard.

124

Re: webhook - Adobe Console I/O and Adobe Runtime I/O - Adobe I/O Cloud Extensibility

@1982luca - when you configure your I/O Events integration, you have 2 options of event delivery: webhook and Runtime action.If you want Runtime action, it's important that it should respond to a "challenge" request. The action should also have "require-adobe-auth: false" if you deploy it with aio app.Here is an example of a Runtime action handling webhook calls: https://github.com/AdobeDocs/adobeio-samples-firefly-basics/blob/master/actions/event-handler/index.js.

142

Re: CORS Issue on uploading files to Workfront API using... - Project Firefly

ok, in that case you could still use the Files SDK to receive the file from the UI. When the Runtime action calls Workfront API, instead of simply giving the file URL, you would stream the file to the post request to upload in the "multipart/form-data" way. Here is a sample code from quick Google search: https://stackoverflow.com/questions/44021538/how-to-send-a-file-in-request-node-fetch-or-node.

Re: CORS Issue on uploading files to Workfront API using... - Project Firefly

Does the workfront API accept a URL to the file? I don't think using the Runtime action as a middleware to upload file is ideal because it makes the performance much worse, and the serverless action itself is not intended to handle files. Instead, the recommendation is to upload the files to Firefly Files SDK, get the files URL, and pass it over to Workfront.You flow would be like this: UI calls Runtime action to get upload URL -> Action returns Files SDK URL -> UI uploads file to Files SDK and ...

Re: Admin Configuration Page Setup - Project Firefly

What kind of API endpoints do you configure? Something you add manually, like a 3rd party system? Do you have different endpoints for prod, stage, etc. like prod.ext-service.net, stage.ext-service.net? And they change per workspace deployment?

Re: Admin Configuration Page Setup - Project Firefly

@shelly-goel - a Firefly app is deployed to a workspace that you specify, which assigns a Runtime namespace and relevant State lib access for it.Speaking about app state, there are 2 separate concepts:build variables: used for building and deploying the app. Those are the values set in .env such as Runtime namespace and auth key, product API key, etc.application variables: used by the application to manage its state (such as a list of customers, product names). You could use aio-lib-state for th...

Re: CORS Issue on uploading files to Workfront API using... - Project Firefly

@shelly-goel - the CORS policy is set by the server (workfront in this case), and you can not bypass it by changing your UI code.The recommended route would be: write a Runtime action to call the workfront API, processes the data, and returns it to the UI for rendering.

110

Re: Email Service - Project Firefly

@kishoreindraganti - the backend of your Firefly app is a set of serverless actions on I/O Runtime. You can write any nodejs code there.However, we don't provide email service. You could use Adobe Campaign for marketing email delivery, or a third party email service (e.g. called from your Runtime actions using REST APIs)

Re: Actions on Schedule - Project Firefly

@kishoreindraganti - yes that is possible using the alarms package in Runtime. Please see the tutorial here: https://adobeio-codelabs-alarms-adobedocs.project-helix.page/

Re: Need help to integrate our web application with illustrator. - Adobe I/O Cloud Extensibility

Hi @ShahinNaji - have you tried this question in the Illustrator forum? It is at https://community.adobe.com/t5/illustrator/bd-p/illustrator.Adobe I/O Cloud Extensibility is the solution when you already have an extension point in Illustrator, and want to set up some web services to extend it (e.g. alternative for a traditional web server).

Re: Need help to integrate our web application with illustrator. - Adobe I/O Cloud Extensibility

Hi @ShahinNaji - do you use some Adobe I/O services or APIs in your web service?

Re: You're right, sorry for the confusion. And yes, pursuing... - Adobe I/O Cloud Extensibility

You can create any action within the project Firefly app, both web action (1 minute timeout) and async (max 30 minutes timeout). Simply run `aio app add action` to add a new one. The important thing is to remove "web: yes" for that action and increase the timeout as you wish. Your manifest.yml should look like:packages: __APP_PACKAGE__: license: Apache-2.0 actions: query-dataset: function: actions/client/index.js web: 'no' runtime: 'nodejs:12' inputs: LOG_LEVEL: debug limits: timeout: 600000 # 1...

Re: Error: getaddrinfo EAI_AGAIN developers.adobe.io - Project Firefly

one more catch: node 14 is currently not the official supported version of aio-cli. Can you try running with node 12?

Re: You're right, sorry for the confusion. And yes, pursuing... - Adobe I/O Cloud Extensibility

You can see how to call your action in async mode here: https://github.com/AdobeDocs/adobeio-runtime/blob/master/guides/asynchronous_calls.md.I understand that your app has a UI as well. So the end user experience on the UI would be:- you trigger the web action (A) to run dataset query- (A) receives your request, calls another action to run the actual dataset query job (B) in an async mode- (A) responds immediately to the UI (without waiting for (B) to complete), e.g. with status "Query is runni...

186

You're right, sorry for the confusion. And yes, pursuing... - Adobe I/O Cloud Extensibility

You're right, sorry for the confusion. And yes, pursuing the other approach (async call for long requests) is strongly recommended.

195

Re: Hi - I assume you are calling your action via "https://y... - Adobe I/O Cloud Extensibility

@kishoreindraganti - thanks for sharing the screenshot. I can see the same output from the `aio app deploy` command.Regardless, it is only an output from the CLI command. You should still be able to call the same URL with adobeioruntime.net - could you please try in Postman? If you develop your app locally by `aio app run`, adobeioruntime.net is used.I will follow up with the team on fixing the CLI output.(Just to clarify: the different domains mentioned above are only applied for the action URL...

210

Hi - I assume you are calling your action via "https://y... - Adobe I/O Cloud Extensibility

Hi @rkishoreindraganti - I assume you are calling your action via "https://your-namespace.adobeio-static.net/...", is that correct?Please try replacing "adobeio-static.net" by "adobeioruntime.net", and try again.The reason why you got this error is that, your action ran longer than 30 seconds and caused a timeout at the CDN "adobeio-static.net".The "adobeioruntime.net" domain has a timeout of 1 minute, which is default for all web actions running on I/O Runtime.That being said, a web request tak...

224

Re: Error: getaddrinfo EAI_AGAIN developers.adobe.io - Project Firefly

Hi @gokula - could you try updating your CLI to the latest version with this command:npm install -g @adobe/aio-cliMake sure that all the plugins are "core" in the output of this command:aio plugins --coreThen run the "aio app init " command again.

127

Re: Creating a Namespace and retrieving the credentials - Adobe I/O Cloud Extensibility

@gokula - selecting Generic under Actions is the right way to go as we don't have yet a template for Launch API. In that action you can write any code, including calling Launch API using node-fetch.Events and CI/CD are optional for the app. It depends on your needs to add them or not. If not now, you can also add them anytime in the future with "aio app add ...".

205

Re: "error": "missing parameter(s) 'tenant'" at Customer... - Project Firefly

@navink386520 - could it be that the tenant value you are using is not correct? and verify the tenant name with Campaign techops?

Re: Error: getaddrinfo ENOTFOUND - Project Firefly

@navink386520 - I couldn't see your entire web page, but my guess is that you are trying to invoke the "get-profiles" action?It requires the Adobe auth token which is not automatically included when you access the localhost URL. On the other hand, it is included if you access the "experience.adobe.com/..." URL outputted by the app run command.I recommend to go through this codelab to understand the details: https://adobeio-codelabs-campaign-standard-adobedocs.project-helix.page/.This is mentione...

Re: Initialization has failed due to: There was an error... - Adobe I/O Runtime

@RossMyronenko- we recommend to use AIO CLI for developing your application with I/O Runtime. It takes care of building, packaging and deploying your actions, without manually working with zip files.More details are available at https://github.com/AdobeDocs/project-firefly.

Re: Is Adobe IO Licensed? - Adobe I/O Runtime

hi @mazumbha, for I/O Runtime, you could apply for the trial using the link above. That should be enough to give you the development access for your SSR use case.

Likes given to

User

Count

Likes from

User

Count

Guidelines

Cookie preferences