#MuleSoft32 debatiendo

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

☁️ 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

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: 

-

-

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?  

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"} 

In Salesforce log history : 

Username-Password Flow Disabled

for Basic connection type is Working fine   

Outh User Name password it throwing above Erros   

I would like to enable or disable an HTTP proxy dynamically based on a YAML property.

service:
  useHttpProxy: "true"

HTTP Request Config:<http:request-config name="service-config">
    <http:request-connection
        protocol="HTTPS"
        host="${service.host}"
        port="${service.port}"
        proxyConfig="#[
            if (Mule::p('service.useHttpProxy') == 'true')
                'proxyConfig'
            else
                null
        ]" />
</http:request-config><http:proxy
    name="proxyConfig"
    host="${proxy.host}"
    port="${proxy.port}" />

I get the following error:

Unable to convert 'proxyConfig' with class 'java.lang.String'
to class 'HttpProxyConfig'
WriterExecutionException:
Unable to convert 'proxyConfig' with class 'java.lang.String'
to class 'HttpProxyConfig'

My understanding is that the proxyConfig attribute expects an HttpProxyConfig object, while my expression returns a String ("proxyConfig"). 

Is it possible to dynamically set the proxyConfig attribute using a DataWeave expression? Because I don't like to have two separate http:request-config definitions (one with a proxy and one without) and select the appropriate one at runtime 

Thank you in advance!