Best solution to present information to end users
-
@Carnival-Boy said:
@scottalanmiller said:
Sharepoint can automate that if you make a job for it.
How does that work?
They are called Workflows. It is one of the key features of SP.
You can also make custom aps that run on SP too.
-
Can you give an example?
-
I'll try to find an example of one. But a quick description of how they are popularly used:
Jane submits a reimbursement form to the reimbursement queue or drop box.
Paperwork automatically determines her manager and routes to the for approval. If denied Jane is notified. If approved to flows on the finance manage to approve. Again if denied Jane is notified otherwise it moved on.
Finally request goes to processing and this could be a human or an API that automatically creates a check for her.
When complete Jane is notified that her reimbursement is paid.
-
I get that. But @Dashrender said he has a problem with old files on his file server that get abandoned or never cleaned up. A common problem, and what that I struggle with myself. What I don't get is how moving those files into Sharepoint will enable them to be cleaned up or archived and deleted correctly.
-
Or to put it another way: I have a problem with people creating new documents and storing them on the file server, then instead of cleaning them up once they are no longer useful (by archiving or deleting), they just leave them there forever. Particularly bad examples might include half-a-gig of jpegs entitled "Office Christmas Party 2004". With Sharepoint, they'd just upload them there, instead of saving them on the file server.
Basically, people add data faster than they remove data - so you get sprawl and eventually it becomes unmanageable. How is that prevented on Sharepoint in a way that can't be done with a file server?
-
We do have workflows for the file server. For example, we might keep scans of documents relating to particular customer projects that are only needed to be kept for 6 months. I could write a script to delete all docs in the relevant sub-directory that are older than 6 months. Or the user could keep them in sub-directories named by year 2010,2011,2012 etc etc, and then once a year delete the oldest sub-directory, so he only keeps recent years.
Of course, this can and will be replicated in Sharepoint. What I'm interested in is what Sharepoint can do to prevent data sprawl that a file server and a bit of scripting or manual user intervention can't.
Of course, I really need to know exactly what @Dashrender meant.
-
@Carnival-Boy said:
I get that. But @Dashrender said he has a problem with old files on his file server that get abandoned or never cleaned up. A common problem, and what that I struggle with myself. What I don't get is how moving those files into Sharepoint will enable them to be cleaned up or archived and deleted correctly.
Oh. A workflow can detect old files and send them for review automatically.
-
@scottalanmiller said:
@Carnival-Boy said:
I get that. But @Dashrender said he has a problem with old files on his file server that get abandoned or never cleaned up. A common problem, and what that I struggle with myself. What I don't get is how moving those files into Sharepoint will enable them to be cleaned up or archived and deleted correctly.
Oh. A workflow can detect old files and send them for review automatically.
so essentially it "bird dogs" abandoned/forgotten/orphaned/loner/hidden/destitute files and says "hey you, do somethin with these ey!!??"
Spoint (which is what AI sharepoint named itself) -
Yes. Lol. That's one way. Or it could clean them up itself!
-
I just googled "spoint". That was a mistake at work.
-
