Skip to main content

#MuleSoft32 personnes en discutent

【Trailhead Academyより、MuleSoft新コース開始&既存コースの名称変更に関するお知らせ 】

MuleSoftの新コース提供の開始、およびコース名変更のお知らせです。

 

<新コース提供開始のご案内>

Anypoint Code Builder (ACB) 対応版の開発基礎コースが正式リリースとなり、コースの公開と申し込み受付が始まりました。 

 

 

<コース名変更のお知らせ>

 下記3コースにつきまして、コース名が変更されましたのでお知らせします。*コース内容に変更はありません。

 

@* カスタマーサクセス日本 *

 

#MuleSoft  #MuleSoft Training & Certification

0/9000
  • You are trying to connect your Salesforce org to Anypoint Platform.
  • You are receiving the error: "Organization is not yet onboarded to GDoT."
  • Request backend provisioning or onboarding for your Salesforce org to GDoT.

 

Hi Team, I am getting the error while connecting salesforce with anypoint platform.

 

 

 

#Salesforce Admin  #MuleSoft Anypoint Platform  #Einstein For Service  #MuleSoft

1 réponse
  1. Hier, à 12:23

    Hi @Prashant Jain

     

     This looks like an onboarding/provisioning issue rather than a tenant-key issue. The error 

    “Organization is not yet onboarded to GDoT”

    generally means the Salesforce org needs to be provisioned/onboarded before the Anypoint Platform connection can be established.  

     

    Please check with your Salesforce/MuleSoft admin or MuleSoft Support/CSM team to confirm the org's GDoT onboarding status. Once onboarding is completed, retry using the Salesforce Org Tenant Key from Setup → MuleSoft → Anypoint Platform Setup  

     

    https://docs.mulesoft.com/access-management/connecting-salesforce-orgs?utm

     

     If you find this response helpful, please mark it as the Accepted Answer, as it may also help other Trailblazers.  

0/9000

Updates to Slack’s plans and pricing

 

Hi Slack Community: I’m writing with some important updates to Slack’s plans and pricing.  

 

We are committed to giving every team an onramp to AI-powered productivity in Slack, and every organization a secure foundation to grow with digital labor. As such, pricing has been simplified, delivering new features across every plan. 

 

Features highlights

  • AI features are being integrated across all paid plans. 
  • AI agents from Agentforce and partner AI apps can now be deployed in all paid plans
  • Every Salesforce customer will get Slack’s free plan, with access to the brand new Salesforce Channels feature, bringing Slack and Salesforce even closer together.
  • We’re enhancing security across all plans, bringing session duration controls and native device management to all of our plans, including Free, and adding SAML-based SSO for Salesforce customers — giving every team a trusted foundation to securely connect their people, data, AI, and agents.

 

Pricing highlights (Read more about the plans on the Slack Plans page)

  • Free subscribers will maintain access to their current features and will gain access to Salesforce channels.
  • Pro pricing will stay the same and will now include core AI features, Salesforce channels and enhanced security. 
  • Business+ plan pricing will increase to $15 from $12.50 per user per month to reflect the significant value added through new advanced AI capabilities and premium Salesforce integrations.
  • We are introducing a new Enterprise+ plan which includes enterprise search in addition to the full Slack feature set including enterprise-grade AI, premium Salesforce integrations and enhanced security, admin controls, governance and compliance (contact your sales rep to learn more).

🔗 LEARN MORE

 

#Slack Community #TrailblazerCommunity #MuleSoft #Tableau

2 commentaires
  1. 1 sept., 23:34

     The pricing changes are pretty clear, and it’s good to see AI features being included across the paid plans. The Salesforce Channels addition should also make things easier for teams already using both platforms. The Business+ price increase will be an important consideration for some teams. 

0/9000
Sara Blair a publié du contenu dans #Jobs

☁️ Salesforce Developers — Ready for Your Next Adventure? 🚀 

 

Innovate! Inc. is looking for a Mid-Level Salesforce Developer to join our team and help build scalable, user-focused Salesforce solutions. 

 

If you enjoy turning business requirements into great Salesforce experiences and have hands-on experience with Experience Cloud, Apex, LWC, Flow, and integrations, this could be a great next step! 💻✨ 

 

🔹 What we’re looking for:

 

☁️ 3+ years of hands-on Salesforce development experience 

🌐 Hands-on Experience Cloud development, including authenticated external-user experiences 

💻 Experience with Apex, Lightning Web Components, Flow & SOQL

🔗 Experience developing or supporting REST/SOAP integrations

🛡️ Understanding of Salesforce security, sharing, profiles, permission sets & external-user access 

🧪 Experience with code reviews, testing, troubleshooting & production support 

🚀 Familiarity with Git, Salesforce CLI/SFDX, deployments & CI/CD processes 

🤝 Ability to collaborate with business analysts and technical teams to build scalable solutions

➕ Experience with Service Cloud and MuleSoft is a plus!

🏅 Preferred certifications include Experience Cloud Consultant, Platform App Builder, Platform Developer I, and JavaScript Developer I. 

 

🏠 Remote within the U.S. 

💰 Salary Range: $100,000–$120,000 

🇺🇸 U.S. Citizenship required

 🔐 Must be able to obtain a Public Trust clearance

📋 Position is contingent upon contract award. 

 

Interested? Take a look! 👇 

 

👉 Learn more and apply:

 

https://innovateteam.my.salesforce-sites.com/InnovatePublicJobBoard/PublicJobPosting?id=a1KVJ00001nrZKf2AM

 

And if someone in your Trailblazer network comes to mind, please tag or share! 🙌☁️ 

 

#Jobs #Salesforce Developer #Experience Cloud #MuleSoft #Lightning Web Components #Remote Opportunities

0/9000
Krzysztof Zimny a posé une question dans * MuleSoft *

Hi, the current version of the SAP JCo connector enforces the name of the containing jar at runtime. 

This will lead to exceptions, if it doesn't match the name (sapjco3.jar).

JCo initialization failed with java.lang.ExceptionInInitializerError: Illegal JCo archive "com.sap.conn.jco.sapjco3-3.1.13.jar".

It is not allowed to rename or repackage the original archive "sapjco3.jar".

Caused by: java.lang.ExceptionInInitializerError: JCo initialization failed with java.lang.ExceptionInInitializerError:

Illegal JCo archive "com.sap.conn.jco.sapjco3-3.1.13.jar". It is not allowed to rename or repackage the original archive "sapjco3.jar".

 

This is a known issue described in the documentation: 

-

https://docs.mulesoft.com/sap-connector/latest/sap-connector-troubleshooting#jco-renaming-conflicts

 

-

https://help.salesforce.com/s/articleView?id=001117810&type=1

 

 

To resolve this error, the maven-shade-plugin should be added to pom.xml which relocate (rewrite) packages to avoid classpath conflicts. Unfortunately, this approach works only at runtime, but not for MUnit tests. Does anyone know how to configure the pom.xml file for the MUnit tests?  

 

5 réponses
  1. 20 août, 12:55

    There is a solution.

    • Define two profiles in the pom.xml file.
    • Profile 1: runtime -> for the runtime environment, Profile 2: test -> for MUnit tests.
    • Load the JCo dependencies for the runtime profile via Maven and use the maven-shade-plugin.
    • For the MUnit tests, the JCo files (sapjco3.jar, sapidoc3.jar, sapjco3.dll, and libsapjco3.so) must be referenced from or downloaded from an artifact repository. They should then be referenced using the attributes <scope>system</scope> and <systemPath>${saplibs}/sapjco3.jar</systemPath>.
    • This solution works both locally in Anypoint Studio and on the server side through a CI/CD pipeline.
0/9000
Petr H a posé une question dans * MuleSoft *

How to report an issue with data in your Public Nexus Repository? 

I tried to find some contact to the repository maintainers, but to no avail. 

 

In group org.hibernate, for artifact hibernate-entitymanager, your maven-metadata.xml lists version 4.2.21.Final-atlassian-5 which doesn't exist in your repository. 

 

Compare: https://repository.mulesoft.org/nexus/repository/public/org/hibernate/hibernate-entitymanager/maven-metadata.xml

with: https://repository.mulesoft.org/nexus/service/rest/repository/browse/public/org/hibernate/hibernate-entitymanager/

 

It breaks things with loose dependencies (that don't refer to some particular artifact version, but rather to a version range). 

It would be good to fix that.

2 réponses
  1. 29 juil., 03:25

    Creating a support case isn't what I'd like to do. It's a public service, while to create a support ticket I need to have an active contract which doesn't make a sense in this case.

0/9000

Hi, My mule application is deployed on cloudhub 2.0. When I am accessing the apis from postman I am getting the response but when users are caling thos apis from salesforce app, they are getting read time out and sometimes success as well. Sometimes the same issue happening from my postman as well. The imp thing is I am unable to see any logs in runtime manager for this read time out. Can anyone help me regarding this?   

1 réponse
0/9000

Hi,    We are running MuleSoft On-Premise and I am trying to identify what the Antivirus Best Practise / Settings (e.g. exclusion paths etc.) are to ensure it doesn't impact the MuleSoft installation is anyone able to assist or point me in the right direction?    Thank you    Dave   

3 réponses
0/9000

I am trying to log in in mulesoft  

With the User and I am reciving below Error in anypoint studio : 

org.mule.runtime.api.connection.ConnectionException: Failed establishing connection with salesforce 

  org.mule.runtime.api.connection.ConnectionException: Failed establishing connection with salesforce 

  Caused by: Invalid status code: 400, response body: {"error":"invalid_grant","error_description":"authentication failure"} 

 

How to resolve this Error : Username-Password Flow Disabled

 

In Salesforce log history : 

Username-Password Flow Disabled

 

2.png

 

 

3.png

 

for Basic connection type is Working fine   

 

Outh User Name password it throwing above Erros   

 

 

 

  

 

#MuleSoft

2 réponses
  1. 12 août, 05:21

    Hi Intkhab — this isn't a credential problem, it's the flow itself being turned off. Salesforce has disabled the OAuth 2.0 Username-Password flow by default (blocked in new orgs, being switched off in existing ones), and it's fully retired in Winter '27 — after which grant_type=password stops returning tokens. That's exactly your "Username-Password Flow Disabled" log entry plus the invalid_grant / authentication failure, even though the username, password, and token are correct. 

     

    Why your "Basic Authentication" connection still works: that MuleSoft connection type uses the SOAP login (username + password + security token), which is a different mechanism from the OAuth username-password flow — so it's unaffected. You can keep using Basic Auth as an immediate unblock today if you need one. 

     

    The proper fix is to move the Salesforce connector to a server-to-server OAuth flow: 

    - OAuth 2.0 JWT Bearer (recommended for MuleSoft to Salesforce): create a Connected App / External Client App with "Use digital signatures" (upload a certificate), pre-authorize the app for the integration user's profile or permission set, then in the connector switch the connection to OAuth JWT Bearer and supply the consumer key, the username, and the private key/keystore. No password stored. 

    - OAuth Client Credentials is the other supported option — a connected app with client credentials enabled and a Run-As integration user. 

    In the Anypoint Salesforce connector you change the connection type from "Username Password" to "OAuth JWT Bearer" (or Client Credentials) and remove the stored password. 

     

    If you specifically need the old flow back short-term, an admin can check Setup - Identity - OAuth and OpenID Connect Settings for "Allow OAuth Username-Password Flows" — but that toggle is going away with the Winter '27 retirement, so treat it as a stopgap, not a fix. JWT Bearer is the durable path. 

     

    Ref: OAuth 2.0 JWT Bearer Flow for Server-to-Server Integration:

    https://help.salesforce.com/s/articleView?id=sf.remoteaccess_oauth_jwt_flow.htm&type=5

0/9000
Nenad Bjelobaba a posé une question dans * MuleSoft *

I am trying to deploy training4-american-ws (from mulesoft training) app to cloudhub 2.0 using anypoint studio, and while on Wi-Fi i always get this error: 

 

Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:3.1.4:deploy (default-deploy) on project training4-american-ws: Failed to deploy artifacts: Could not transfer artifact c4a3bb0a-a224-4d98-8ed2-d888355c80db:training4-american-ws:jar:mule-application:1.0.0 from/to anypoint-exchange-v3 (

https://maven.anypoint.mulesoft.com/api/v3/organizations/c4a3bb0a-a224-4d98-8ed2-d888355c80db/maven/runId/d90b03c8-e643-4554-8f56-c257c2ca780b

): status code: 500, reason phrase: Internal Server Error (500) -> [Help 1] 

 

, however when i am on cable internet i am able to deploy successfully.  

Why it won't deploy using Wi-Fi, and is there any fix for this?

5 réponses
  1. 11 août, 09:22

    Hi @Nenad Bjelobaba

     

     

    Happy to hear that now it's working. Although it's a really weird behaviour. 

    But now it's clear the issue is on AnypointStudio network settings, try to have a look there, just in case there is something misconfigured. 

     

    Best

0/9000