Skip to main content
Groupe

Apttus and Salesforce Enthusiasts

A one stop shop for the Apttus and Salesforce enthusiast, this group is for sharing news and information around Apttus, Salesforce or technology in general. If you super excited about Apttus and Salesforce then this group is for you. Come join the conversation!

When I change assignee for my approval rule 'GxP Enabled Approval', I get below error when I try to hit the approval rule.

Error:

{faultcode:'soapenv:Client', faultstring:'Apttus_Approval.ApprovalSystemException: Error creating approval requests: SObject row was retrieved via SOQL without querying the requested field: Apttus_Proposal__Proposal__c.Opportunity_AEs_Manager__c (Apttus_Approval)', }

 

I have changed the assignee for other approval rules as well and they are working fine. Could someone please help?

2 réponses
  1. 3 août 2023, 13:31

    Hey Mikey, thanks for replying! Opportunity_AEs_Manager__c is a lookup field to user's manager. User is populated on the records I'm using. Is there anything I'm missing?

0/9000

Hi,

 

I have an X-Author presto app that is launched from Salesforce. The goal is to query the record and display the data fields from a single Salesforce record, then run a macro and produce a PDF that is then attached to the Salesforce record.

 

Everything is working when I use a static record id value in the Query. How can I pull in the record id based on which record is leveraging the button? Am I able to pass it into the button as a parameter that can be leveraged?

 

Thanks!

1 commentaire
  1. 22 janv. 2023, 15:32

    One way to do this is to create a custom button on the Salesforce object that launches the X-Author presto app and pass the record ID as a parameter. You can use the {!URLFOR($Action.ObjectName.ButtonName, Id)} merge field to pass the record ID as a parameter in the URL of the custom button.

0/9000

I'm reviewing licenses assigned to my users and licenses stated in my contract, and there is a disconnect. Here is a list of the products in the contract

SF-CLM-ULT-G01-->PUBLIC SECTOR CLM + X-AUTHOR - 1 APP-REQUIRES FOUNDATION (1-50 USERS)

SF-CSM-ULT-G01-->PUBLIC SECTOR CSM - REQUIRES PUBLIC SECTOR CLM AND FOUNDATION (1-50 USERS)

SF-CLM-ULT-G02-->PUBLIC SECTOR CLM USER (51-100 USERS)

 

Here is a list of permission sets in the environment: 

Apttus_Admin

Apttus_CLM_Platform_Requester_1

Apttus_CLM_Platform_Requester_2

Apttus_Read_Only

Apttus_Requestor_Approver

Apttus_Contract_Manager

Apttus_SRM_User_Admin

Apttus_Template_Admin

 

Can someone help me align the permission sets to the licenses? Thanks in advance!!

0/9000

Regarding Apttus X-Author for Excel, 

I am building an x-author application and requirement is complex so I need to build some Macros, I found that X-author provide action for Macro but I am not sure how to use it. It would helpful if anyone can suggest some approach. 

 

Thanks

0/9000

Can anyone confirm if X-Author supports the LineItemSchedule object (Opportunity Product Schedules)? Thanks!

8 commentaires
0/9000

Hello, I'm looking to see if any Apptus-Salesforce customers have deployed Apptus in an org separate from their main sales cloud environment.  A customer of mine is looking to have Apptus as a centralized quoting engine that serves multiple CRM environments. 

0/9000

Apttus Customer Aramark was dealing with company-wide inefficiencies costing time and money. While Aramark’s legal department excelled at negotiating and managing contacts on an individual basis, it struggled with contract maintenance at the corporate level.

 

Read the attached success story that shows how Aramark streamlined and automated global contract process with Apttus CLM

0/9000

Since the release of Winter 20, I have a group of users that are not able to access X-author for Excel. The error is "Can't access this page: We don't support this browser. Try opening this page in a supported browser." Our standard is Chrome, and it is the default browser set for those computers. 

 

Has anyone else run into this issue? It is only happening for users in the UK and it all worked fine until Winter 20 release.

3 commentaires
0/9000