App Builder

When looking for an answer to this question, I've only seen recommendations for how you should manage the use of third party databases. Is there an database offering included with App Builder?@sarahxxu 

Hi, I have my server setup on AWS EC2 with CentOS7. Node: V16.18.1 npm: V8.19.2 I have installed AIO cli successfully through terminal, however when I'm trying to do aio login - it asks for browser authentication which I'm unable to access in the EC2 machine.  Eventually, the request times out after 2 minutes.      

Hello all,I have built an application which uses the Photoshop API for processing images for a client. Several PSDs the client has supplied work perfectly. However, they provided me a new PSD that fails with the following error: Smart Object Edit Failure (type InternalServiceError).  I admit limited knowledge with Photoshop to begin with, but as far as I can tell, this new PSD has a smart object layer named "watermark" just like the ones that work. I can't see a noticeable difference. Does anyone have an ideas? And if anyone from Adobe is hanging out here, my feedback would be that this error is not terribly useful. A little more detail would go a long way in troubleshooting.Anyway, thank 

Trying to follow these steps to create an App Builder to consume Adobe Commerce events: https://developer.adobe.com/commerce/events/get-started/configure-commerce/When getting to the step of running: bin/magento events:subscribe observer.catalog_product_save_after --fields=sku --fields=stock_data.qty it return a 500 Internal Server Error.Unsuccessful request: `POST https://api.adobe.io/events/[org_id]/[project_id]/[workspace_id]/providers/[event_provider_id]/eventmetadata` resulted in a `500 Internal Server Error` response:{"reason":"Adobe I/O Events Runtime Error. Request id: [request_id].","message":"Unexpected response from upstream http service. Please take a note of the http response `x-request-id` header for debugging/support."}Not sure how to debug this issue or if any other steps was required not listed in the developer adobe page shared above.

Hi, for my project I have created 4 runtimes - dev, qa, stage & prod.  When I publish the app in all the runtimes - it gets available globally on www.  How can I restrict this at org level - where in users outside my org should not be able to access dev, qa & stage.   Example - https://12345-mywebsite-dev.adobeio-static.net - should be blocked   

Is it possible that for the same runtime action request, one part of the logs will be shown with one activation ID and another part with another? We have implemented an action used for Server Side Render, and we have implemented a list of strategic applicative logs like:Start SSR -> as first row code of the action..URL Request path XXX -> for each external HTTP client executionURL Response <> -> as response of the above execution ..End SSR --> as last row code of the action and during the log troubleshooting we are occurring that NOT all the activation ID are started with log "Start SSR" and ended with "End SSR". Thanks in advance!

I am getting following error while starting aem server, 24.07.2023 12:26:59.517 *ERROR* [0:0:0:0:0:0:0:1 [1690181819507] GET /libs/granite/core/content/login.html HTTP/1.1] org.apache.sling.engine.impl.SlingMainServlet service: Uncaught Problem handling the requestjava.lang.IllegalArgumentException: Could not find configuration for domain 'magento'at com.day.cq.commons.impl.ExternalizerImpl.externalLink(ExternalizerImpl.java:308) [com.day.cq.cq-commons:5.12.16]at com.day.cq.commons.impl.ExternalizerImpl.externalLink(ExternalizerImpl.java:299) [com.day.cq.cq-commons:5.12.16]at com.canon.core.rewriter.LinkRewriterXF.startElement(LinkRewriterXF.java:82) [com.canon.aem.core:1.38.0.SNAPSHOT]at com.adobe.acs.commons.rewriter.impl.VersionedClientlibsTransformerFactory$VersionableClientlibsTransformer.startElement(VersionedClientlibsTransformerFactory.java:370) [com.adobe.acs.acs-aem-commons-bundle:6.0.6] Basically I want to validate CQ Link configuration but I could not able to logi

Hi, We have deployed a custom react app on App builder with API mesh configured for 2 endpoints - 1. Magento 2. AEM My API mesh endpoint & Magento & AEM endpoints are working fine individually. However, when we are trying to retrieve data from Magento in API mesh, it is failing at some point.  I would like to understand where APP builder stores its logs?  I tried running few commands - but all of them responded blank. Like - aio app logsaio runtime logsaio rt activation ls Datetime Status Kind Version Activation ID Start Wait Init Duration Entity─────────────── ──────── ──────── ──────── ─ ───────────── ───── ──── ──── ──────── ────── Can someone help me on how to debug the application on APP Builder Stage runtime? 

We are integrating AEM CIF with 3rd Party commerce(Hybris). We using Diconium connector(https://github.com/diconium/commerce-cif-graphql-integration-hybris) and deployed it in Adobe I/O.We have done CIF Cloud Configs to enable Commerce in AEM , which will help us in using Product/Category Picker. we need to do some customization at connector level so that this AEM Commerce , can fetch Products from the store configured in Config. But to do those Customization we are not able to see logs of diconium connector in Adobe I/O. We need these logs to understand the diconium connector project flow.

I'm working on custom component where author will provide file name and file path in dialog. When user clicks on the file name then file will be get downloaded. This functionality is working absolutely file in author but failing in publish instance for XML,Excel and word files. I noticed one extra folder(dam:failedRenditions) for these types on publish instance. Can someone explain why theses renditions are failing? and why i'm unable to download only XML,DOC,Excel file on publish instance? 

After running npm install command I am trying to deploy the code using "aio app deploy" but I ended up with below error.  "stack": "ModuleParseError: Module parse failed: Unexpected token (1:0)\nYou may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See › https://webpack.js.org/concepts#loaders\n> <!--\n| Copyright (c) Microsoft Corporation.\n| \n at handleParseError (/usr/local/lib/node_modules/@adobe/aio-cli/node_modules/webpack/lib/NormalModule.js:982:19)\n at › /usr/local/lib/node_modules/@adobe/aio-cli/node_modules/webpack/lib/NormalModule.js:1101:5\n at processResult (/usr/local/lib/node_modules/@adobe/aio-cli/node_modules/webpack/lib/NormalModule.js:806:11)\n at › /usr/local/lib/node_modules/@adobe/aio-cli/node_modules/webpack/lib/NormalModule.js:866:5\n at /usr/local/lib/node_modules/@adobe/aio-cli/node_modules/loader-runner/lib/LoaderRunner.js:407:3\n at iterateNorma

Hi,I Follow this link https://experienceleague.adobe.com/docs/commerce-operations/configuration-guide/files/disable-module-output.html but its not work for me .so what do i need to for this solution , can u please suggest me other solution.Thanks.

I am trying deploy code from local to adobe runtime using "aio app run" but I get below error, Module not found: Error: Can't resolve '@adobe/aio-sdk & Module not found: Error: Can't resolve 'openwhisk'    root@mario # aio app run How you use /aio-cli provides us with important data that we can use to make our products better. Please read our guide for more information on the data we anonymously collect, and how we use it. https://developer.adobe.com/app-builder/docs/guides/telemetry/ ? Would you like to allow /aio-cli to collect anonymous usage data? Yes Telemetry is on! Nice, you are helping us improve /aio-cli If you would like to turn telemetry off, simply run `aio telemetry off` ℹ using remote actions ℹ building actions.. › Error: action build failed, webpack compilation errors: › [ › { › "moduleIdentifier": "/Users/mario/Documents/actions/send-action/index.js", › "moduleName": "./actions/send-action/index.js", › "loc": "1:17-42", › "message": "

Hello,I'm trying to use simple script to make POST API call to external endpoint using Adobe IO. Under this link (https://developer.adobe.com/runtime/docs/guides/reference/runtimes/) I found information that node-fetch should be built in and work out of the box. However, when I try to run my action I'm receiving this error: { "error": "fetch is not defined" } If I'm trying to import it using "import fetch from 'node-fetch';" I'm receiving: { "error": "Initialization has failed due to: SyntaxError: Cannot use import statement outside a module\n at NodeActionRunner.init (/nodejsAction/services/runner.js:91:109)\n at doInit (/nodejsAction/services/service.js:225:31)\n at initCode (/nodejsAction/services/service.js:161:24)\n at /nodejsAction/routes/action.js:25:13\n at Layer.handle [as handle_request] (/node_modules/express/lib/router/layer.js:95:5)\n at next (/node_modules/express/lib/router/route.js:144:13)\n at Route.dispatch (/node_modules/express/lib/router/route.js:114

Hello,I'm trying to use simple script to make POST API call to external endpoint using Adobe IO. Under this link (https://developer.adobe.com/runtime/docs/guides/reference/runtimes/) I found information that node-fetch should be built in and work out of the box. However, when I try to run my action I'm receiving this error:  { "error": "fetch is not defined" }  If I'm trying to import it using "import fetch from 'node-fetch';" I'm receiving:  { "error": "Initialization has failed due to: SyntaxError: Cannot use import statement outside a module\n at NodeActionRunner.init (/nodejsAction/services/runner.js:91:109)\n at doInit (/nodejsAction/services/service.js:225:31)\n at initCode (/nodejsAction/services/service.js:161:24)\n at /nodejsAction/routes/action.js:25:13\n at Layer.handle [as handle_request] (/node_modules/express/lib/router/layer.js:95:5)\n at next (/node_modules/express/lib/router/route.js:144:13)\n at Route.dispatch (/node_modules/express/lib/r

Do we have any documentation on creating section component, I want to create a component in which i can drop multiple component , where i can add some styling in the component like background-color and on top of that i can drag and drop other component?I am new to AEM developmentThanks 

I created a barebones App Builder Project in Developer Console with 1 action calling an AEM servlet. The goal is to call this action from a third-party application and preserve the "require-adobe-auth: true" annotation. I've seen references to the IMS Auth library, but that takes a client id/secret to generate a token. My Project in Developer Console doesn't have a Credentials section where I can grab this information. The Headless App example just takes out the "require-adobe-auth" annotation: https://developer.adobe.com/app-builder/docs/resources/barcode-reader/barcode/. It'd be great if there was an example on how to achieve this  How I envision this working:We call the App Builder Action using the service credentials provided in the Developer Console Project. With that access token, the App Builder Action will be able to call the AEM endpoint. We manage the AEM access level of the App Builder service credentials through Admin Console, assigning it to an exi

On 10th May, 2021, Adobe I/O Runtime has added support for Node 14 for JavaScript actions. Node 14 will be made default after June 10, 2021. For the next 90 days we will have pre-warm containers for both Node 14 and 12.After 90 days, we will have pre-warm container only for Node 14.  Action: Please update your actions if you are using this kind. If you do not update your actions after 90 days from today, your actions will not use the default version and If you do not update your actions within 90 days, your actions will not have access to pre-warm containers. You can check the version running this command: aio runtime action get <ACTION NAME>orwsk action get <ACTION NAME>If  you don’t see “kind”: “nodejs:14”, then you have to update your action. Resources for Reference: Check this: https://git.corp.adobe.com/bladerunner/openwhisk-runtime-nodejs/ Public docs: https://github.com/AdobeDocs/adobeio-runtime/bl

Help shape the future of Adobe Experience Cloud!The all-new Adobe Experience Cloud Customer Feedback Panel provides you opportunities to talk about the topics you care most about and help set the vision for Adobe Experience Cloud applications. You will have the opportunity to engage directly with Adobe product and development experts who are building Adobe Experience Cloud applications and services, and you'll receive updates on how your feedback is being integrated.As a member of our feedback panel, you will get invitations to participate in a wide variety of feedback activities (surveys, usability tests, product previews, strategic roadmap discussions and beta tests). Through these activities, you will have a direct connection to the Product Managers, designers, and developers who create the products you use every day, and have the opportunity to learn from fellow customers. We've always valued feedback from our customers via UX, Beta Testing, Customer Advisory Board and so on.

Hello there, In two weeks from now (week of April 26th, 2020) we will update the way I/O Runtime handles activations for successful blocking invocations.This is the new behavior:By default, successful blocking invocations will not produce an activation record, thus running “wsk activation list” will not list any of these. Logs are still recorded and can be retrieved using the activation ID  - this is still being sent to the client invoking the actionBlocking invocations that failed will produce an activation record and will appear in “wsk activation list”Developers can force creating an activation record for successful blocking invocations by including this header “X-OW-EXTRA-LOGGING: on” in the requestNon-blocking invocations don’t change, “wsk activation list” will return all the activation IDs created by non-blockingPublic docs have been updated [0]You might ask why we are doing this change: performance and developer convenience. We can squeeze more performance b