Sharepoint 2007 批准电子邮件
在我们公司，我们有一个 Sharepoint 2007 服务器，我们用它来跟踪我们的汽车。 我试图实现的是有一个 aspx 页面，您可以在其中选择汽车列表中的一辆车，然后单击“请求”。如果您这样做，该页面必须切换到另一个文本，显示“正在进行汽车请求”之类的内容（当然，如果下一个人进入此页面，则将这辆车隐藏在汽车列表中）并向某人发送一封电子邮件，其中包含两个按钮： “接受”“拒绝”。如果他点击“拒绝”，汽车状态必须再次设置为可用，以便其他人可以再次请求这辆车。如果他点击“接受”，另一个人会收到一封电子邮件，告诉他 person1 请求了这辆车，并且已经得到 person2 的批准。使用等待状态更改的工作流程可以轻松创建此电子邮件，但是如何创建一个链接来更改汽车列表中的汽车状态字段以及在 aspx 请求页面中需要什么代码？
提前致谢！ 孟菲斯
in our Company we have a Sharepoint 2007 Server which we are using to keep track of our cars.
What I try to achieve is to have a aspx page where you can select a car of the cars list and then click "request". If you did that the page must switch to another text saying something like "car request in progress" (and of course hide this car in the cars list if the next person enters this page) and send an email to someone which contains two buttons: "accept" "decline". If he clicks "decline" the cars status has to be set to available again so someone else can do a request for this car again. if he clicks "accept" another person gets an email telling him that person1 requested this car and this has been approved by person2. this emails are easy to create using workflows which are waiting for the status to change but how can i create a link which changes a cars statusfield in the cars list and what code do i need in the aspx request page?
Thanks in advance!
MemphiZ
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
创建一个链接，单击该链接将代表用户运行适当的操作。如果您使用工作流程，这就像更改 items 属性并处理 item-change 事件一样“简单”。确保避免周期性变化。
这可以通过在 URL 中编码项目 GUID（可能还有列表和操作以及您想要的任何其他内容）来轻松完成； GUID 可以与 SharePoint 对象模型一起使用进行查找。
也许上面的操作可以使用 SPD 来完成，而无需单独的/“代码”ASPX，但我不碰那堆“乐趣”。
编辑评论：
在我的场景中，我们只是将链接编码为
http://foo.com/whatever.aspx?id={THEGUID}。 aspx 处理程序只是读取查询参数。项目编辑功能使用标准 SharePoint 列表权限。双重提交被拒绝，因为在处理链接后，项目被修改为新状态，不接受所述链接操作（因此再次单击链接只会导致无操作）。在开始工作之前绘制出总体状态图可以节省大量时间。Make a link that, when clicked, will run the appropriate action on the users behalf. If you are using workflows, this is as "simple" as changing the items property and letting the item-change event be handled. Make sure to avoid cyclic changes.
This can be done trivially by encoding the items GUID (and perhaps list and action and whatever else you want) in the URL; the GUID can be used with the SharePoint Object Model for the lookup.
Perhaps the above can be done using SPD without a separate/"code" ASPX, but I don't touch that pile of "fun".
Edit for comment:
In my scenario we just encoded the link as
http://foo.com/whatever.aspx?id={THEGUID}. The aspx handler just read the query parameters. Item editing ability used standard SharePoint list permissions. Double-submissions were rejected because after the link is handled the item modified to be in a new state which does not accept said link-action (thus clicking the link again simply resulted in no-operations). Working out a total state-diagram before starting work can save lots of time.