Oracle CRM On-Demand - 使用任务状态更新服务请求状态
我们的服务组正在使用 CRM On-Demand，但我遇到了应用程序限制，想知道是否有人有解决方法或只是一些关于如何实现我们的目标的一般想法。
在应用程序中，我们的主要重点是围绕服务请求并推动用户为与关闭相关的所有活动创建任务。例如，客户打来电话，我们需要技术资源进行回电以详细诊断问题，因此将任务分配给该资源。一旦该任务被标记为已完成，我希望更新状态。我尝试使用 JoinFieldValue() 创建工作流程，但不起作用。我尝试了一种更基本的方法，并尝试仅在服务请求上的一个字段中填充任务的状态，但这也不起作用。
在帮助文件中进一步调查后发现，活动对象与服务请求对象之间存在某种关系，但反之则不然。
那么，是否有其他人遇到此限制并找到其他方法来使任务状态更改更新服务请求的状态？
（另外，我想尝试避免为此目的编写自定义 Web 服务，这就是我尝试使用应用程序中的工具的原因）
提前感谢您的任何想法！
We're using CRM On-Demand for our Service Group and I'm running into an application limitation and am wondering if anyone has a workaround or just some general ideas on how to accomplish our goal.
In the application, our major focus is around the Service Request and driving for users to create Tasks for all Activities related to working towards closure. For example, a customer calls in and we need a technical resource to make a return call to diagnose the issue in detail, so a Task is assigned to that resource. Once that Task has been marked as completed, I'd like the Status to be updated. I tried creating a workflow using JoinFieldValue(), which wasn't working. I tried a more basic approach and tried to just have a field on the Service Request be populated with the Status of the Task, but that did not work either.
Upon further investigation in the Help File, there is a relationship from the Activity object to the Service Request object, but not one the other way.
So, has anyone else run into this limitation and found some other method to have a Status change on the Task update the Status of a Service Request?
(Also, I'd like to try and avoid writing a custom web service for this purpose, which is why I'm trying to use the tools in the app)
Thanks in advance for any ideas!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
实际上，如果我很好地理解您的问题与工作流跨对象有关。
当您需要使用解决方法时，OCOD 不会管理此类工作流程。
为了涵盖跨对象工作流程，您有很多可能性：
我更喜欢第一个解决方案。
actually, if I well understood your issue is related on workflow cross object.
OCOD doesn't manage this type of workflow when you need to use workaround.
In order to cover a cross object worklflow you have many possibilities:
I would prefer the 1st solution.